E' stato finalmente pubblicato un buon documento per il capacity planning di SharePoint 2010. Un ottimo segnale, augurio di buoni deployment (visto che tra pochi giorni tutti partiremo con i nuovi deployment di SharePoint 2010).

http://www.sharepointcommunity.it/links/Lists/Links/DispForm.aspx?ID=4

Riporto di seguito un po' di numeri estratti dal documento Microsoft:

Web application limits

The following table lists the recommended guidelines for Web applications. 

Limit	Maximum value	Limit type	Notes
Content database	300 per Web application	Supported	With 300 content databases per Web application, end user operations such as navigating to the site or site collections are not affected. But admin operations such as creating a new site collection will experience performance degradation. It is also suggested to user PowerShell to manage the Web application when a significant number of Content databases is present
Zone	Five per Web application	Boundary	The number of zones defined for a farm is hard coded to 5. Zones include Default, Intranet, Extranet, Internet, and custom.
Managed path	20 per Web application	Supported	Managed paths are cached on the Web server, and CPU resources are used to process incoming requests against the managed path list. If you plan to exceed twenty managed paths in a given Web application, we recommend you test for acceptable system performance.

 

Web server and application server limits

The following table lists the recommended guidelines for Web servers on the farm. 

Limit	Maximum value	Limit type	Notes
Application pools	10 per Web server	Supported	Maximum number is determined by hardware capabilities.This limit is dependent largely upon: ·         The amount of RAM allocated to the front end servers·         The workload that the farm is serving – the user base and the usage characteristics (the process of a single highly active application pools can reach 10 GB or more)

Content database limits

The following table lists the recommended guidelines for content databases. 

Limit	Maximum value	Limit type	Notes
Content database size	200 GB per Content database	Supported	We strongly recommended limiting the size of content databases to 200 GB to help ensure system performance.Content database sizes up to 1 terabyte are supported only for large, single-site repositories and archives with non-collaborative I/O and usage patterns, such as Records Centers. Larger database sizes are supported for these scenarios because their I/O patterns and typical data structure formats have been designed for, and tested at, larger scales.A site collection should not exceed 100 GB unless it is the only site collection in the database.

 

Site collection limits

The following table lists the recommended guidelines for site collections. 

Limit	Maximum value	Limit type	Notes
Web site	250,000 per site collection	Supported	You can create a very large total number of Web sites by nesting the subsites, For example: a shallow hierarchy with 100 sites, each with 1,000 subsites, is a total 100,000 Web sites, or a deep hierarchy with 100 sites, each 10 levels deep also containing a total of 100,000 Web sites. The maximum recommended number of sites and subsites is 250,000 sites. Note that Web deletion can have significant impact on the Site’s availability, access to the site and subsites will be limited during the time of Web deletion. Also high concurrency of subsite creation might fail beyond a certain pace
Site Collection Size	100 GB per site collection	Supported	A site collection should not exceed 100 GB unless it is the only site collection in the database.Certain site collection actions, such as site collection backup/restore or Move-SPSite, cause large Microsoft SQL Server® operations which can have performance impact or fail if other Site collections are active in the same database.

  

List and library limits

The following table lists the recommended guidelines for lists and libraries. For more information, see the "Designing Large Lists and Maximizing List Performance" white paper accessible from http://technet.microsoft.com/en-us/library/ff608068(office.14).aspx. 

Limit	Maximum value	Limit type	Notes
List View Threshold	5,000	Threshold	Specifies the maximum number of list or library items that a database operation, such as a query, can process at one time, outside of the daily time window set by the administrator during which queries are unrestricted.
List View Threshold size for auditors and administrators	20,000	Threshold	Specifies the maximum number of list or library items that a database operation, such as a query, can process at one time when performed by an auditor or administrator with appropriate permissions. This setting works in conjunction with Allow Object Model Override.
List row size	8,000 bytes per row	Boundary	For each SharePoint list or library item, it is only allowed to occupy 8000 bytes in total in the database. 256 bytes are reserved for built-in SharePoint columns, which leaves 7744 bytes for end-user columns. For details on how much space each type of field consumes, please look at the Column Limits.
File size	2GB	Boundary	The default maximum file size is 50 MB. This can be increased up to 2 GB, but a large volume of very large files can impact farm’s performance
Documents	50,000,000 per library	Supported	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.
Items	tens of millions per list	Supported	You can create very large lists using standard views, site hierarchies, and metadata navigation. This value may vary depending on the number of columns in the list and the usage of the list.
Rows Size Limit	six table rows internal to the database used for a list or library item	Supported	Specifies the maximum number of table rows internal to the database used for a list or library item. To accommodate wide lists with many columns, each item may be wrapped over several internal table rows, up to six rows by default. This is configurable by the Farm administrators through the Object Model only. The Object Model method is SPWebApplication.MaxListItemRowStorage.
List View Lookup Threshold	eight join operations per query	Threshold	Specifies the maximum number of joins allowed per query, such as those based on lookup, Person/Group, or workflow status columns. If the query uses more than eight joins, the operation is blocked. This does not apply to single item operations. When using the maximal view via the OM (by not specifying any view fields), SharePoint will return up to the first eight lookups.
Bulk operations	100 items per bulk operation	Boundary	User interface allows a maximum of 100 items to be selected for bulk operations.

Page limits

The following table lists the recommended guidelines for pages. 

Limit	Maximum value	Limit type	Notes
Web parts	25 per page	Threshold	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.

 Security limits 

Limit	Maximum value	Limit type	Notes
Number of SharePoint groups an User can belong to	5,000	Supported	This is not a hard limit but it is consistent with Active Directory® guidelines. There are several things that affect this number:·         The size of the user token·         The groups cache: we have a table that caches the number of groups an user belongs to as soon as those groups are user for in ACLs·         The security check time: as the number of groups a user is a member of increases, the time required for access check increase as well.
Users in a Site Collection	2 million per site collection	Supported	You can add millions of people to your Web site by using Microsoft Windows® security groups to manage security instead of using individual users. This limit is based on manageability and ease of navigation in the user interface. When you have many entries (security groups of users) in the site collection (more than one thousand), you should user PowerShell to manage users instead of the UI. This will provide a better management experience.”
Active Directory Principles/Users in a SharePoint group	5,000 per SharePoint group	Supported	SharePoint allows you add users or Active Directory groups to a SharePoint group.Having up to 5,000 users (or Active Directory groups or users) in a SharePoint group provides acceptable performance. The actions affected by this Limit are: a) Fetching user to validate permissions, this operation grows incrementally with growth in number of users in a group. b) Rendering the membership of the view will always require time.
SharePoint groups	10,000 per site collection	Supported	Beyond 10,000 groups, the time to execute operations is increased significantly especially for adding a user to an existing group, creating a new group and rendering the group views.
Security principal: size of the Security Scope	5,000 per Access Control List (ACL)	Supported	The size of the scope impacts the data used for a security check calculation. This calculation occurs each time the scope changes. There is no hard limit, but the bigger the scope is the longer the calculation takes.

 

Other limits

The following table lists the recommended guidelines for other objects. 

Limit	Maximum value	Limit type	Notes
Subsite	2,000 per site view	Threshold	The interface for enumerating subsites of a given Web site does not perform well as the number of subsites surpasses 2,000. Similarly, the All Site Content page and the Tree View Control performance will degrade significantly as the number of subsites grows.