Site object Guidelines for acceptable performance Notes Scope of impact when performance degrades
50,000 per content database
Total farm throughput degrades as the number of site collections increases.
150,000 per Web application
This limit is theoretical, and is dependent largely upon:
Performance of the database server on which the configuration database resides.
Performance of the Web servers in the farm.
Network bandwidth between the Web servers and the database server.
This is not a hard limit, and assumes a single database server. Your environment may not be able to host this many site collections per Web application. Distributing content databases across additional database servers can increase the effective limit of the number of site collections per Web application. You should perform testing to determine the actual effective limit in your environment.
250,000 per site collection
You can create a very large total number of Web sites by nesting the subsites. For example, 100 sites, each with 1000 subsites, is 100,000 Web sites. The maximum recommended number of sites and subsites is 125 sites with 2,000 subsites each, for a total of 250,000 sites.
2,000 per Web site
The interface for enumerating subsites of a given Web site does not perform well as the number of subsites surpasses 2,000.
5 million per library
You can create very large document libraries by nesting folders, using standard views and site hierarchy. This value may vary depending on how documents and folders are organized, and by the type and size of documents stored.
2,000 per view
Testing indicates a reduction in performance beyond two thousand items. Using indexing on a flat folder view can improve performance.
Document file size
50MB (2GB max*)
File save performance is proportional to the size of the file. The default maximum is 50 MB. This maximum is enforced by the system, but you can change it to any value up to 2 GB.
Library, file save performance
2,000 per Web site
Testing indicates a reduction in list view performance beyond two thousand entries. For more information about large lists, see White paper: Working with large lists in Office SharePoint Server 2007.
256 per list
This is not a hard limit, but you might experience list view performance degradation as the number of field types in a list increases.
2,000 per document library
4,096 per list
This is not a hard limit, but you might experience library and list view performance degradation as the number of columns in a document library or list increases.
Library and list view
50 per page
This figure is an estimate based on simple Web Parts. The complexity of the Web Parts dictates how many Web Parts can be used on a page before performance is affected.
20 per Web application
20 managed paths is a soft limit. Managed paths are cached on the Web server, and CPU resources are used to process incoming requests against the managed path list. You should test for performance before exceeding 20 managed paths in a single Web application.
The following table lists the recommended guidelines for people objects.
People object Guidelines for acceptable performance Notes
Users in groups
2 million per Web site
You can add millions of people to your Web site by using Microsoft Windows security groups to manage security instead of using individual users.
5 million per farm
This number represents the number of profiles which can be imported from a directory service, such as Active Directory, into the people profile store.
Approximately 2,000 per ACL (Access Control List) on any securable object (scope)
The total size of the ACL on scopes can be no larger than 64kb. Because each security principal is approximately 32 bytes in size, there can be no more than approximately 2,000 security principals or less for each scope. If this limit is reached, indexing of items in that scope, and all items below that scope, to fail.
Also, because SharePoint Groups are expanded during the indexing process, having more than 2,000 users or Directory Groups in a SharePoint group and using that group for securing scopes may cause indexing of items secured with these groups, and all items below them, to fail.
This limit only occurs when Windows Integrated Authentication is utilized.
The following table lists the recommended guidelines for search objects.
Search object Guidelines for acceptable performance Notes
One per SSP
Maximum of 20 per farm
Office SharePoint Server 2007 supports one content index per SSP. Given that we recommend a maximum of 20 SSPs per farm, a maximum of 20 content indexes is supported.
Note that an SSP can be associated with only one index server and one content index. However, an index server can be associated with multiple SSPs and have a content index for each SSP.
50,000,000 per content index
Office SharePoint Server 2007 supports 50 million documents per index server. This could be divided up into multiple content indexes based on the number of SSPs associated with an index server.
500 per SSP*
This is a hard limit enforced by the system.
500 per content source*
This is a hard limit enforced by the system.
1,000,000 per SSP
This is the tested limit.
200 per site
This is a recommended limit per site. We recommend a maximum of 100 scope rules per scope.
25 per site
These are used for a grouped display of scopes through the user interface.
10,000 per SSP
We recommend a maximum 10,000 crawl rules irrespective of type.
15,000 per site
We recommend a maximum of 10 Best Bets and five synonyms per keyword.
500,000 per SSP
These are properties that are discovered during a crawl.
100,000 per SSP
These are properties used by the search system in queries. Crawled properties are mapped to managed properties. We recommend a maximum of 100 mappings per managed property.
200 per relevance level
This is the maximum number of sites in each of the four relevance levels.
This is the maximum recommended number of URLs that should be removed from the system in one operation.
Number of individual log entries in the crawl log.
The following table lists the recommended guidelines for logical architecture objects.
Logical architecture object Guidelines for acceptable performance Notes
Shared Services Provider (SSP)
3 per farm (20 per farm maximum)
5* per farm
The number of zones defined for a farm is hard coded to 5.
99 per SSP
This limit includes the number of Web applications on child farms consuming resources on this SSP.
Internet Information Services (IIS) application pool
8 per Web server
Maximum number is determined by hardware capabilities.
50,000 per Web application
100 per Web application
50,000 per database
The following table lists the recommended guidelines for physical objects.
Physical object Guidelines for acceptable performance Notes
1 per SSP*
Application servers running Excel Calculation Services
Because 100 content databases are supported for each query server, the number of query servers required per farm is based on the number of content databases in the farm. For example, if there are 500 content databases in your farm, you will need at least 5 query servers.
Web server/database server ratio
8 Web servers per database server
The scale out factor is dependent upon the mix of operations.
Web server/domain controller ratio
3 Web servers per domain controller
Depending on how much authentication traffic is generated, your environment may support a greater number of Web servers per domain controller.