評估容量及效能規範和 SharePoint Server 2013 的 eDiscoveryEstimate capacity and performance for compliance and eDiscovery for SharePoint Server 2013

摘要:了解如何規範、 eDiscovery 及大型文件存放庫可以 effect 容量和效能的 SharePoint Server 2013。Summary: Learn about how compliance, eDiscovery, and large-scale document repositories can effect capacity and performance in SharePoint Server 2013.

規範功能集,例如就地保留與查詢及匯出資料下保留、 效果處理和 SharePoint Server 2013 時所使用的儲存需求。Compliance feature sets, such as in-place holds and querying and exporting data under preservation, effect the processing and storage requirements in SharePoint Server 2013 when used.

就地保留的儲存需求Storage requirements for in-place holds

就地保留保留編輯和刪除內容提供法律動作的原始版本。就地保留套用到整個網站。例如,如果網站集合的根網站置於 [保留] 完成的網站集合也是音樂。設為就地保留套用至文件、 頁面和清單。網站置於 [保留之後,第一次編輯或刪除所有項目會保留在保存保留庫之 SharePoint 網站。此位置所在原本在網站上位於內容。網站大小增加時顯示與多少內容時存在保留已啟用並加入新內容時變更關聯率。作法是處於合法持有大部分的內容不是新。就地保留的儲存空間造成影響預期會是低,因為使用者並不會主動變更內容。如需詳細資訊,請參閱SharePoint Server 中的 eDiscovery 及就地保留An in-place hold preserves edited and deleted content to make the original version available for legal actions. In-place holds apply to a complete site. For example, if the root site of a site collection is put on hold, the complete site collection is also on hold. An in-place hold applies to documents, pages, and lists. After a site is put on hold, all items that are edited for the first time or deleted, are put in the Preservation Hold Library for the SharePoint site. This location is where the content was originally located on the site. The size of the site increases at a rate that correlates with how much of the content existed when the hold was enabled and is changed when new content is added. In practice, most content on legal hold is not new. The effect on storage for in-place holds is expected to be low because users are not actively changing content. For more information, see eDiscovery and in-place holds in SharePoint Server.

EDiscovery 查詢及匯出對其他搜尋查詢的影響Effect of eDiscovery queries and export on other Search queries

SharePoint Server 2013 已呼叫可讓您跨組織 SharePoint 內容和 Exchange Server 2013 信箱執行 eDiscovery 查詢的大小寫管理員網站集合類型。eDiscovery 查詢通常是複雜高度和寬度的範圍。這些查詢需要更多搜尋系統上的處理時間,且可能會影響其他使用者會遇到的搜尋回應時間。SharePoint Server 2013 has a site collection type called Case Manager that allows you to execute eDiscovery queries across your organization's SharePoint content and Exchange Server 2013 mailboxes. eDiscovery queries are usually complex and wide in scope. These queries require more processing time on the Search system and potentially affect the search response time that other users experience.

下列指導方針可協助您了解這些查詢對其他使用者搜尋體驗的影響:The following guidelines can help you understand how these queries affect Search experiences for other users:

  • 當您將多個來源新增至 eDiscovery 查詢時,您會增加執行的查詢數目。As you add more sources to an eDiscovery query, you increase the number of executed queries.

  • 當您將更多的字詞新增至 eDiscovery 查詢時,您會增加 eDiscovery 查詢的影響。As you add more terms to an eDiscovery query, you increase the effect of your eDiscovery queries.

  • 當您將多個運算子 (例如 AND、 OR NEAR) 新增至 eDiscovery 查詢時,您會增加 eDiscovery 查詢的影響。As you add more operators (such as AND, OR, NEAR) to an eDiscovery query, you increase the effect of your eDiscovery queries.

在測試實驗室,我們使用 eDiscovery 查詢的 350 針對 10 來源已執行的字詞。查詢會傳回 150000 項目的總數。然後我們所匯出的項目。若要執行這項測試,我們會表示其他類型都能如預期在系統上執行的搜尋查詢的搜尋服務系統上執行五個模擬的負載。In our lab tests, we used an eDiscovery query of 350 terms that ran against 10 sources. The query returned a total of 150,000 items. We then exported those items. To perform this test, we executed five simulated loads on the Search service system, which represented other types of search queries that are expected to run on the system.

我們測試顯示 eDiscovery 查詢可以增加使用者觀察儘 100%的查詢延遲。如果您執行接近容量適用於您的使用者搜尋查詢時,您可能會考慮執行 eDiscovery 查詢並匯出至具有較小的效果在使用者搜尋查詢的非尖峰時間。Our tests show that eDiscovery queries can increase query latencies that users observe by as much as 100 percent. If you run close to capacity for your user search queries, you might consider running eDiscovery queries and exports during non-peak hours to have a smaller effect on user search queries.

匯出的影響Effect of Export

執行 eDiscovery 查詢之後,一般作業會匯出資料。匯出巨集指令,期間 eDiscovery 查詢傳回的內容是一次下載一個檔案。我們已執行一組測試我們下載檔案並更新 SharePoint 項目。匯出 SharePoint 部署將無法新增重要的負載。執行 [匯出] 動作測試時在伺服器陣列服務大約 100 每秒要求數目。不在 100 個要求匯出動作進行只有約五個每秒要求數目。After you run eDiscovery queries, a common operation is to export the data. During the export action, content that the eDiscovery query returned is downloaded one file at a time. We ran a set of tests where we downloaded files and updated SharePoint items. Export did not add a significant load on the SharePoint deployment. We ran the export action in our tests while the farm served about 100 requests per second. Out of the 100 requests only about five requests per second were made by the export action.

請注意對 Exchange Server 2013 的匯出影響可能會不同。Exchange Server 2013 查詢是變數,特別是 eDiscovery 通常是長和複雜的查詢。Note that the effect of export on Exchange Server 2013 may be different. Exchange Server 2013 queries are variable, particularly eDiscovery queries that are often long and complex.

與 SharePoint Server 2013 大型文件存放庫Large-scale document repositories with SharePoint Server 2013

除了法規遵循與 eDiscovery 功能之外的 SharePoint Server 2013 大型文件存放庫功能已不變更大幅從 SharePoint Server 2010。本節中我們參照規模測試報告超大型文件存放庫 (SharePoint Server 2010),並會指出包含 SharePoint Server 2013 文件存放庫的案例的差異。下列各節摘要說明主要差異。Aside from the compliance and eDiscovery features, the SharePoint Server 2013 large scale document repositories feature has not changed significantly from SharePoint Server 2010. In this section we refer to Scale test report for very large scale document repositories (SharePoint Server 2010), and point out differences for scenarios that involve SharePoint Server 2013 document repositories. The following sections summarize the main differences.

指引放在前端網頁伺服器上的互動式的服務應用程式Guidance for putting interactive service applications on front-end web servers

SharePoint Server 2010 的指導建議您將放在不同的層的服務應用程式。在 SharePoint Server 2013 中建議的互動式的服務應用程式置於當成前端網頁伺服器執行的電腦。如需詳細資訊,請參閱SharePoint Server 2013 的容量計劃Guidance for SharePoint Server 2010 advised you to put service applications on a separate tier. In SharePoint Server 2013 we recommend that you put the interactive service applications on computers that run as front-end web servers. For more information, see Capacity planning for SharePoint Server 2013.

在 SharePoint Server 2013 中的搜尋Search in SharePoint Server 2013

SharePoint Server 2013 Search Service 應用程式合併的 SharePoint Server 2010 搜尋和 FAST Search Server 2010 for SharePoint 整合的搜尋平台與其他功能。如需詳細資訊,請參閱擴充 SharePoint Server 中的網際網路網站的搜尋SharePoint Server 中的搜尋架構的概觀The SharePoint Server 2013 Search Service application merges the SharePoint Server 2010 Search and FAST Search Server 2010 for SharePoint into a unified search platform with additional functionality. For more information, see Scale search for Internet sites in SharePoint Server and Overview of search architecture in SharePoint Server.

有效的檔案 I/O 和 SQL Server 增強功能Efficient File I/O and SQL Server improvements

在 SharePoint Server 2013 中的有效檔案 I/O 是在其中的檔案分割成多個片段儲存並個別進行、 更新及進行資料流處理一起當使用者要求該檔案儲存方法。這會導致更有效率的檔案更新為只更新的部分會寫入到 SQL Server。使用大型檔案時非常有效有效率的檔案 I/O。小型檔案可以看到所需的磁碟儲存空間小型增加。使用有效的檔案 I/O 的直接結果是要更新的文件的輸送量已獲得改善。Efficient File I/O in SharePoint Server 2013 is a storage method in which a file is split into pieces that are stored and updated separately, and streamed together when a user requests the file. This results in more efficient file updates as only the updated pieces are written to SQL Server. Efficient File I/O is very effective when you use it with large files. Small files can see a small increase in the disk storage that is required. A direct result of using Efficient File I/O is that the throughput to update documents is improved.

其他增強功能搭配 SQL Server 2008 R2 SP1 功能與輸送量來尋找文件的連結修正與警示處理。Other improvements use SQL Server 2008 R2 with SP1 features and throughput to find documents for link fix-up and alert handling.

SharePoint Server 2013 資料儲存在 SQL Server 資料表中。為了允許 SharePoint 清單中最大的可能欄數,SharePoint Server 2013 會在單一列無法容納資料時,在資料庫中建立多個列。這稱為列換行。Column limits

在 SharePoint Server 2013 中更新欄限制。如需詳細資訊,請參閱SharePoint Server 2016 的軟體界限及限制Column limits are updated in SharePoint Server 2013. For more information, see Software boundaries and limits for SharePoint Server 2016.

另請參閱See also


評估容量及效能規範和 SharePoint Server 2013 的 eDiscoveryEstimate capacity and performance for compliance and eDiscovery for SharePoint Server 2013

在 SharePoint 中設定 eDiscoveryConfigure eDiscovery in SharePoint Server