Tuesday, May 24, 2011

SharePoint:Limits and details in Moss

For SharePoint Portal Server, here's an extract from the Capacity Planning whitepaper:
It is important to understand the ramifications of the different features and functions of the SharePoint Portal Server solutions to size the system so that the performance of the system is good.
The following table lists some of the SharePoint Portal Server objects and describes their recommended use. "Typical" indicates comfortable and well tested; "maximum" indicates that the system can support that number, but not without some performance ramifications or
special configurations.
An asterisk (*) indicates a hard limit; no asterisk indicates a tested or supported limit.
  • Portal sites (full) - typically 2 ... maximum 15 *
  • Portal sites (child) - typically 10 ... maximum 100 *
  • Areas - typically 1,000 ... maximum 10,000
  • Best Bets - typically 1,000 ... maximum 25,000
  • Area depth - typically 5 ... maximum 20 *
  • User profiles - typically 50,000 ... maximum 1,000,000
  • Audiences - typically 500 ... maximum 10,000
  • Audience memberships - typically 500,000 ... maximum 5,000,000
  • SSO credentials - typically 100,00 ... maximum 100,000
  • Search indexes - typically 3 ... maximum 32
  • Content sources -typically 25 ... maximum 250
  • Search scopes - typically 25 ... maximum 250 *
  • Indexed documents per content index - typically 100,000 ... maximum 5,000,000
  • Indexed documents - typically 2,500,000 ... maximum 20,000,000
  • Thesaurus entries - typically 1,000 ... maximum 10,000
  • Alerts - typically 50,000 ... maximum 1,000,000
  • Team sites - typically 10,000 ... maximum 250,000
  • Personal sites - typically 10,000 ... maximum 250,000

No comments:

Post a Comment

SharePoint - Cannot convert a primitive value to the expected type 'Edm.Double'. See the inner exception for more details If y...

Ad