The SharePoint search engine consists of 6 components, namely crawl components, content processing components, analysis processing components, index components, query processing components, and search management components. You can deploy these 6 components to multiple servers within a SharePoint farm, forming a SharePoint search farm that fits your needs, the main reference for the search farm's architecture design is crawl capacity, and Microsoft divides the search field into large, medium, and small farms based on the capacity of the crawl. For more details, refer to: Search Overview in SharePoint Server 2013 and plan for enterprise search architecture in SharePoint Server 2013.
SharePoint Search engine architecture diagram
Content Volume |
Search Architecture |
10 million item (+) |
Small Search server farm |
10 million-40 million items |
Medium Search Server farm |
40 million-100 million items |
Large Search server farm |
As an example of a small search topology, Microsoft testing can support 10 million projects and measure that it can crawl 50 documents per second and serve 10 queries per second. For the crawl rate of 50 documents per second, the first full crawl requires a search of 55 hours to crawl 10 million items.
Small Farm Server Topologies
The following is a description of the hardware requirements for this small farm:
Machine server |
Application or database server |
Storage Storage |
Ram |
Processor |
A, B |
Application server with query processing and indexing components |
GB |
+ GB |
1.8 GHz 4x CPU Core |
A, B |
An application server with crawl, search administration, analysis, and content processing components. |
GB |
8 GB |
1.8 GHz 4x CPU Core |
A, B |
A database server with all search databases. |
Gb |
+ GB |
1.8 GHz 4x CPU Core |
Search Component Description:
Search Component Name |
Description |
Crawl Components |
Crawl content sources to collect crawled properties and metadata from crawled items and send this information to the content processing component |
Content Processing Components |
Transforms a crawled item and sends it to the index component. This component also maps crawled properties to managed properties |
Analysis Processing components |
Perform search analysis and usage analysis |
Index component |
Searches the processed items from the content processing component and writes them to the search index. This component can also process incoming queries, retrieve information from the search index, and send the result set back to the query processing component |
Query processing component |
Parses an incoming query. This helps improve accuracy, improve retrieval, and improve relevance. The query is sent to the index component, which returns a set of search results for the query |
Search Administration Components |
Run a system process for the search, adding and initializing a new instance of the search component |
Search Database Description:
Search database name |
Description |
Crawl Database |
Stores trace information and historical information about crawled items, such as documents and URLs. Information such as the last crawl time, the last crawl ID, and the type of update (add, update, delete) during the last crawl is also stored. |
Link Database |
Stores the unhandled information extracted by the content processing component and information about the search click. This information is parsed by the analysis processing component. |
Analysis Report Database |
The results of the storage usage analysis. |
Search Administration Database |
Store Search configuration Data |
Blog to: "Sharepoint2013 Search learning Notes of the search Framework Simple Overview (a)"
Reproduced A simple overview of the search architecture for SharePoint 2013 Search Learning Notes