Posted on October 11, 2010 by Kelly Rusk in SharePoint
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 opening the site or site collections are not affected. But administrative operations such as creating a new site collection will experience decrease in performance. We recommend that you use Windows PowerShell to manage the Web application when a large number of content databases are present, because the management interface becomes slow and difficult to navigate. |
| Zone | 5 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.Exceeding 20 managed paths per Web application adds more load to the Web server for each request.If you plan to exceed twenty managed paths in a given Web application, we recommend that you test for acceptable system performance. |
| Solution cache size | 300 MB per Web application | Threshold | The solution cache allows the InfoPath Forms service to hold solutions in cache in order to speed up retrieval of the solutions. If the cache size is exceeded, solutions are retrieved from disk, which may slow down response times. You can configure the size of the solution cache by using the Windows PowerShell cmdlet Set-SPInfoPathFormsService. For more information, see Set-SPInfoPathFormsService. |
PDF Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Tags: 
One Response
[...] Know Your Limits: Capacity Planning in SharePoint 2010 | Concurrency Blog (tags: sharepoint architecture sql) Like this:LikeBe the first to like this post. [...]