What?
How to calculate the number of Web Front Servers (WFEs) / Web Servers required for a SharePoint 2010 site?
Why?
Capacity Planning in SharePoint 2010 is a complicated and confusing topic and there's not a whole lot of really good documentation around it.
There are so many factors that affect your planning in this area that it is almost impossible for anyone to come up with a solid number. Your performance would be affected by the server hardware, the client hardware, the concurrency rate of your users, the throughput rate required, the response time your organization deems acceptable etc.
These are just the factors that we actually CAN calculate into our formulae. Additionally, your general network load and other factors that could cause interference with your expected performance will from time to time wreck havoc with your stats, but for the most part we can make a good judgment call as to the type of farm setup that would be required in most cases.
How?
Planning capacity is different for intranet/collaboration portals (that require a lot of read/write operations) from public facing sites built on SharePoint 2010 (that only require a lot of read operations).
There are a number of excellent blog posts and documentation from Microsoft that explains about capacity planing for SharePoint 2010 sites.
Here are a few of the best posts that I have come across:
For a public facing site, the main driving factors are requests/views per second (RPS) and total number of concurrent users.
An experienced solutions architect has adviced me that a typical WFE with 4 Core CPUs and 16 GB RAM which is the recommended hardware for a public facing SharePoint 2010 site in a production environment can handle 200-300 concurrent users with 300-500 page views per sec for a public facing site.
How to calculate the number of Web Front Servers (WFEs) / Web Servers required for a SharePoint 2010 site?
Why?
Capacity Planning in SharePoint 2010 is a complicated and confusing topic and there's not a whole lot of really good documentation around it.
There are so many factors that affect your planning in this area that it is almost impossible for anyone to come up with a solid number. Your performance would be affected by the server hardware, the client hardware, the concurrency rate of your users, the throughput rate required, the response time your organization deems acceptable etc.
These are just the factors that we actually CAN calculate into our formulae. Additionally, your general network load and other factors that could cause interference with your expected performance will from time to time wreck havoc with your stats, but for the most part we can make a good judgment call as to the type of farm setup that would be required in most cases.
How?
Planning capacity is different for intranet/collaboration portals (that require a lot of read/write operations) from public facing sites built on SharePoint 2010 (that only require a lot of read operations).
There are a number of excellent blog posts and documentation from Microsoft that explains about capacity planing for SharePoint 2010 sites.
Here are a few of the best posts that I have come across:
- http://technet.microsoft.com/en-US/library/031b0634-bf99-4c23-8ebf-9d58b6a8e6ce.aspx
- http://www.cjvandyk.com/blog/Lists/Posts/Post.aspx?ID=100
- http://blogs.technet.com/b/wbaer/archive/2007/07/06/requests-per-second-required-for-sharepoint-products-and-technologies.aspx
- https://skydrive.live.com/view.aspx/Public-presentations/Sharepoint%202010%20capacity%20planning%20and%20sizing%20sheet.xlsx?cid=71febae9593b0994
For a public facing site, the main driving factors are requests/views per second (RPS) and total number of concurrent users.
An experienced solutions architect has adviced me that a typical WFE with 4 Core CPUs and 16 GB RAM which is the recommended hardware for a public facing SharePoint 2010 site in a production environment can handle 200-300 concurrent users with 300-500 page views per sec for a public facing site.
No comments:
Post a Comment