Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Internet Sites Search Architectures for SharePoint Server 2013 PreviewOverview                         This model illustra...
Upcoming SlideShare
Loading in …5

SharePoint 2013-internet-sites-search-model


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

SharePoint 2013-internet-sites-search-model

  1. 1. Internet Sites Search Architectures for SharePoint Server 2013 PreviewOverview This model illustrates a medium-size Internet Sites farm architecture that has been tested by Microsoft®. Architecture requirements can vary depending on the composition of the data that is crawled (size of items and formats). This example illustrates the For more information about search components, see the following model: Search Architectures for SharePoint® type of search components needed and how many of each. Use this Server 2013 Preview ( example as a starting point for planning your own search environments. ?LinkId=258643).SEARCH COMPONENTS EXAMPLE TOPOLOGYApplication components Medium Internet Sites farm (~85 page views per second) This farm illustrates a fault-tolerant SharePoint Server 2013 Preview search farm topology that is optimized Index Index component — The index component is the logical representation of an index for a corpus that contains 3,400,000 items. The example farm processes 100-200 documents per second, replica. depending on the language, and it accommodates 85 page views per second and 100 queries per second. Index partitions Index replicas · You can divide the index into discrete · Each index partition holds one or more portions called index partitions, each index replicas that contain the same holding a separate part of the index. information. · An index partition is stored in a set of · You have to provision one index Host A Host B Host C files on a disk. component for each index replica. Web servers · The search index is the aggregation of · To achieve fault tolerance and Web server Web server Web server all index partitions. redundancy, create additional index Web front-end Web front-end Web front-end replicas for each index partition and distribute the index replicas over multiple application servers. Query processing Query processing component Analyzes and processes search queries and Application Host D Host E Host F results. servers Application server Application server Application server Admin Search administration Search administration component Analytics Admin Admin · Runs system processes that are essential T Crawl Content processing Crawl Content processing Crawl Content processing to search. Crawl Crawl component · Only one search administration · Crawls content based on what is component can be active per Search specified in the crawl databases. Host G Host H Host I service application. · Add crawl components to address capacity requirements and to increase crawl performance. Application server Application server Application server Query Processing Query Processing Query Processing Content processing component Content processing Carries out various processes on the Replica Index partition 0 Replica Replica crawled items, such as document parsing Analytics processing component Replica Index partition 1 Replica Replica Analytics and property mapping, before feeding the Carries out search analytics and usage items to the index component. F analytics. Host G DatabaseSearch databases server SharePoint databases Crawl db Search admin db Search administration database Search admin db Crawl db · Stores search configuration data. Link db Analytics db · Only one search administration Crawl db Crawl database All other SharePoint databases database per Search service application. · Stores the crawl history · Manages crawl operations · Each crawl database can have one or more crawlers associated with it. A Link db Link database Stores the information extracted by the content processing component and also Analytics db Analytics reporting database stores click-through information. Stores the results of search usage analytics.PERFORMANCE CONSIDERATIONS HARDWARE REQUIREMENTSApplication servers hosting search components These requirements apply to the medium Internet Sites search topology.Things to consider Reasoning Application servers – minimum resource requirements RCache The query and its results are cached in key-value pairs: the query being the key and the results being Search RAM Hard disk Processor the value. For each query there is an approximate 50% cache ratio. This means that if you have a usage pattern of 200 queries per second, about 100 queries will be sent to the search index and the component on other 100 queries will be cached. Results from the cache have lower query latency than those from the physical the search index. For example, results for front-page queries that are run repeatedly are likely to be server cached. Index 48 GB for production use in a single server or in a multiple 500 GB additional disk space, preferably a separate disk All components: component server farm. volume/partition.Continuous crawl We recommend that you enable continuous crawl with an interval of 1 minute instead of the default 64-bit, 4 cores minimum, 8 cores recommended. interval of 15 minutes. You can enable continuous crawl on SharePoint content sources only. Analytics 24 GB for production use in a single server or in a multiple 300 GB additional disk space, preferably a separate disk processing server farm. volume/partition. componentAnonymous access With anonymous access, users don’t have to use credentials to log into a SharePoint Internet site. In addition, anonymous queries are cached, so they are cheaper because of lower query latency. You Crawl 24 GB for system drive. 80 GB for system drive. must enable anonymous access in two locations: on the web front-end and on the site itself. component You must have sufficient space for the base installation and D sufficient space for diagnostics such as logging and ContentQuery latency Query latency is influenced by caching, anonymous access and by other factors such as the number debugging, for creating memory dumps, and for other processing and complexity of query rules that are applied and triggered. Also, consider the disks on which the operations. For production use, you also need additional component search index is stored; a disk that has multiple spindles can improve the access speed of the disk and free disk space for regular operations. Maintain twice as reduce query latency. much free space as you have RAM for production Query 48 GB for production use in a single server or in a multiple environments. processing server farm. component Search 24 GB for production use in a single server or in a multiple administration server farm. component Database servers — minimum resource requirements Hardware Minimum requirements component Processor 64-bit, 4 cores for small deployments 64-bit, 8 cores for medium deployments Ram 8GB for small deployments 16GB for medium deployments Hard disk 80GB for system drive © 2012 Microsoft Corporation. All rights reserved. This documentation is preliminary and subject to change. To send feedback about this documentation, please write to us at