SharePoint Capacity Planning

SharePoint Capacity Planning There is no hard limit enforced by the system, the most useful parementes for the capacity design are listed in the table below.  The capacity planning for MOSS 2007 from Microsoft can be found at http://technet2.microsoft.com/Office/en-us/library/9994b57f-fef8-44e7-9bf9-ca620ce207341033.mspx?mfr=true and is summarized here Object Scope Guideline for optimum performance Comment Site collections Database 50,000 Total throughput degrades as the number of site collections increases. Web sites Web site 2,000 The interface for enumerating subsites of a given Web site does not perform well much beyond 2,000 subsites. Web sites Site collection 250,000 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,100 Web sites. Documents Folder 2,000 The interfaces for enumerating documents in a folder do not perform well beyond a thousand entries. Documents Library 2 million You can create very large document libraries by nesting folders. Security principals Web site 2,000 The size of the access control list is limited to a few thousand security principals, in other words users and groups in the Web site. Users Web site 2 million You can add millions of people to your Web site by using Microsoft Windows security groups to manage security instead of using individual users. Items List 2,000 The interface for enumerating list items does not perform well beyond a few thousand items. Web Parts Page 100 Pages with more than 100 Web Parts are slow to render. Web Part personalization Page 10,000 Pages with more than a few thousand user personalizations are slow to render. Lists Web site 2,000 The interface for enumerating lists and libraries in a Web site does not perform well beyond a few thousand entries. Document size File 50 MB The file save performance degrades as the file size grows. 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 (2047 MB) if you have applied Windows SharePoint Services Service Pack 1. Object Guidelines for acceptable performance Notes Scope of impact Site collections per Web application 50,000 Total farm throughput degrades as the number of site collections increases. Farm Web sites per site collection 250,000 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. Site collection Subsites per Web site 2,000 The interface for enumerating subsites of a given Web site does not perform well as the number of subsites surpasses 2,000. Site view Documents per library 5 million 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. Library Items per container 2,000 Testing indicates a reduction in performance beyond two thousand items. Using indexing on a flat folder view can improve performance. List view 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 (2047 MB) if you have applied Windows SharePoint Services Service Pack 1. For more information, see Configuring large file support in Installing and Using Service Packs for Windows SharePoint Services. Library, file save performance Lists per web site 2,000 Testing indicates a reduction in list view performance beyond two thousand entries. List view Field types per list 256 This is not a hard limit, but you may experience list view performance degradation as the number of field types in a list increases. List view Web parts per page 100 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. Page Web Part personalization per page 10,000 Testing indicates a reduction in performance beyond a few thousand user personalizations. Page Features per Web application 250 As the number of activated features per Web application increases, so does the memory usage of the w3wp process. This value is an estimate; your environment may support more or fewer activated features for a given Web application. Farm People objects Object Guidelines for acceptable performance Notes Users in groups per web site 2 million You can add millions of people to your Web site by using Microsoft Windows security groups to manage security instead of using individual users. Security principals per web site 2,000 The size of the access control list is limited to a few thousand security principals, in other words users and groups in the Web site. User profiles per farm 5,000,000     Personalization and Search objects Object Guidelines for acceptable performance Notes Search indexes 1 per SSP*   Content sources 250   Search scopes 250   Best bets 25,000   Audiences 10,000   Audience memberships 5,000,000   Indexed documents per content index 5,000,000   Indexed documents 20,000,000   Thesaurus entries 10,000   Alerts 1,000,000    Logical architecture objects Object Guidelines for acceptable performance Notes Shared service providers 3 (20 max)   IIS app pools 8 Maximum number is determined by hardware capabilities. Web applications 4 Maximum number is determined by hardware capabilities. Web applications per SSP 99   Site collections per Web application 50,000   Zones per farm 5* The number zones defined for a farm is hard coded to 5. Content databases per Web application 100   Site collections per database 50,000   Physical objects Object Guidelines for acceptable performance Notes Index server 1 per SSP*   Excel calculation server No limit   Search server No limit   Query server 1 per database*   WFE servers per database server 8*   WFEs per Domain Controller 3 Depending on how much authentication traffic is generated, your environment may support a greater number of WFEs per domain controller. Level Performance limits Site collection 2,000 subsites of any site is the recommended limit. The same content database is used for an entire site collection. This may affect performance in operations such as backup and restore. Site 2,000 libraries and lists is the recommended limit. Library 10,000,000 documents is the recommended limit. 2,000 items per view is the recommended limit. Folder 2,000 items per folder is the recommended limit