Guidance

In conclusion the load increases for the Activity Stream is heavily weighted toward the WFEs.

​	​1x0x1	1x1x1​	​2x1x1
WFE load increase (users)​	16​	15​	15​
WFE load increase (%)​	123%​	​100%	​43%
​	​	​	​

For capacity planning, plan as you would for a general SharePoint environment. Any page that contains the Activity Stream web part will need to add about 30% capacity for concurrent user load.

From what we can tell we scale in a similar fashion to a SharePoint environment (which makes sense, running on a SharePoint environment). Performance degradation is most noticeable in the WFEs. Since a farm environment is designed to scale out the WFEs horizontally, this is straightforward issue to address.

The AS has quite an increase in CPU Load as well, but as shown in the charts, the utilization was between 5% to 20%. This wasn't a factor (for these test) in performance.

Memory stats are not included. The server environment seems to have held around 50% to 80% utilization, and didn't seem to play a role in performance. Having said this, more memory never hurts.

Typically when asked something like "can the system handle 200k users", this means 200k users/day. You'll need to calculate the number of users/sec. Not counting spikes in traffic or other types of non-constant load, you can calculate the users/sec metric like so:

Given below is a user metric of nnnK users

• = nnnK users/day
• = nnn,000 / 24 hours / 60 minutes / 60 seconds
• = n / 86400
• = n users/sec

For example:

• 200K users = 200,000 / 86400 = 2.35 user/sec
• 30K users = 30,000 / 86400 = .35 users/sec

You can take these metrics and compare them to the VSTS Load in the tables above.