Capacity planning
Meeting load requirements
NewsGator believes customers should size the SharePoint Server which will be running the User Profile Service Application (and the NewsGator managed service) at 25% above the projected sizing based on the profile service by itself. Size web front ends to account for 30% to 100% more load than with SharePoint alone, based on the number of web front ends in your SharePoint environment, according to the chart below.
For further details see, Aurea Social - Testing Procedure and Results Used to Establish Capacity Guidelines.
|
Number of WFEs |
1 |
2 |
3+ |
|
% sizing increase suggested to run Social Sites |
100% |
50% |
30% |
Alternatively, if you don't have extra capacity in your web front ends to handle additional load and will be adding similar-capacity web front ends, you should add about 45% to your number of WFE’s from your base sizing to retain the same performance. In NewsGator's tests, the database server is not seeing significant pressure.
As you add web front ends without adding application servers, your application server(s) may become your bottleneck, however based on NewsGator testing this only happens if you have far more WFE's than you do application servers (with two WFE's and one application server, the WFE's are still the bottleneck).
Meeting storage requirements
NewsGator suggests planning for Social Sites's databases to require an amount of storage per user for every 180 days of data retained in the database, in accordance with the charts below.
So, for example, if set to retain 720 days = 180 days x 4 of social data, and your Social Sites users are very active in Social Sites (add a relatively large amount of content it it) you would want to allot 0.25 MB x 4 = 1.0 MB of storage per user with an active SharePoint profile in your system.
If you have a good idea of how many of your users are actively contributing to Social Sites (the NewsGator licensing information page in Central Administration gives you an idea of this), you may prefer to use the numbers in the first row instead, meaning, for our example, you would allot 1.10 MB x 4 = 4.40 MB per active user of Social Sites. NewsGator recommends using both calculation methods for each database, and using the larger result.
Actual storage required in practice may vary for you, depending on how actively your user base uses Social Sites.
| NewsGator social database | ||
|---|---|---|
|
Calculation method |
Less active user base |
More active user base |
|
MB per user that actively contributes to Social Sites |
0.03 |
1.10 |
|
MB per user with an active SharePoint profile |
0.01 |
0.25 |
| NewsGator Reporting Database | ||
|---|---|---|
|
Calculation method |
Less active user base |
More active user base |
|
MB per user that actively contributes to Social Sites |
0.002 |
0.100 |
|
MB per user with an active SharePoint profile |
0.001 |
0.030 |
| NewsGator News Manager Database | ||
|---|---|---|
|
Calculation method |
Less active user base |
More active user base |
|
MB per user that actively contributes to Social Sites |
0.0 |
2.0 |
|
MB per user with an active SharePoint profile |
0.0 |
0.5 |