SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

How do we calculate the capacity planning for SharePoint handling an Internet Presence site. What will be the server topology? How many WFE and so on?

If for instance if we need to identify the server hits 300,000 hits as peak traffic and 15% more on the subsequent years.

How do we arrive at the best server topology?

share|improve this question

I seem to rememeber reading somewhere that you were not allow to publish SharePoint performence metrics. So the only place I know that has this kind on info is msdn.

I referenced this page a lot for sp2007:

And the tool:

But for 2010, i think you have to use:

share|improve this answer
i downloaded the SharePoint Capacity Planning Tool , but it requires a prerequisite System Center Capactity Planner V2.0 , I am not able to find this – Thomson Jan 28 '11 at 10:25
looks like it is a dead product… – djeeg Jan 28 '11 at 11:54

There are no hard rules you can follow as they will be different in every enviroment.

Topology is based on your requirements. Technet some diagrams for some basic deploment methodologies:

You need to determine your fault tolerance requirements in combination with your performance requirements to really determine the optimum configurations.

Some Variables affecting performance: Bandwidth CPU Memmory Cache Proxies Services utilized in farm Web Apps App Pools

There are some guidlines in the capacity guides , but they are just to get you started. MS may say 10000 users per WFE with 16GB Ram, but that may be lower if you increase your cache sizes and consume more memmory, or higher if you add more RAM, or minimze the services you are using. From a performance standpoint you will really need to do some testing.

The SharePoint Administration toolkit has visual studio module you can use for load testing.

Run that and monitor the counters here and you will start to get to the numbers you can rely on.

The good thing about SharePoint is it is very scalable. If you notice your WFE's are overloaded, spin antoher one up and add it to the farm (assuming load balanced), same for any of the services, if Search is not accetable, determine the bottle neck and add query, crawl, or even dedicated db servers.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.