索引分区 [英] Index Partition
问题描述
我最近读到索引分区的建议限制是1000万个文档.我们有一个索引分区和1,260万个文档.是基于性能的一千万个限制，还是存在超过一千万个破坏"的风险.
I recently read the recommended limit for an Index Partition is 10 million documents. We have one Index Partition and 12.6 million documents. Is the 10 million limit based on performance or is there risk that above 10 million something "breaks".
服务器场仅用于存储和检索，响应时间非常长.
The Farm is used solely for storage and retrieval, and response time is great.
Paul F.
推荐答案
1000万是受支持的限制，而不是边界.索引作为文件存储在已部署搜索索引组件的服务器场服务器上，该文件的一部分将存储在服务器RAM中.索引大小取决于项目数，大小 例如，文本繁重的文档将增加索引大小，因为索引将所有单词的位置存储在文档中.
10 million is a supported limit, not a boundary. Index is stored as file on those farm servers to which you deployed the Search index component, and a portion of that file will be stored in server RAM. Index size has a dependencies on number of items, size of the documents, etc. For example, text heavy documents will increase index size since the index stores the position of all words in a document.
增加索引分区的数量会减少索引分区中的项目数，这会减少托管分配给索引分区的查询组件的查询服务器上所需的RAM和磁盘空间." 请参阅: SharePoint Server 2010搜索的预期性能和容量要求. (虽然很旧，但在概念上仍然有效.)
"Increasing the number of index partitions decreases the number of items in the index partition, and this reduces the RAM and disk space that is needed on the query server that hosts the query component assigned to the index partition." See: Estimate performance and capacity requirements for SharePoint Server 2010 Search. (Old but still valid on the concepts.)
参考
这篇关于索引分区的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
