16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 9: Capacity Planning 221<br />

■ The single server with SQL Server configuration supported a sustained<br />

throughput of 15 operations per second at 80 percent average CPU consumption.<br />

The CPU was the limiting factor here. To scale this server to support more<br />

users would require going to a small server farm.<br />

■ The small server farm supported a sustained throughput of 18 operations per<br />

second at 80 percent average CPU consumption on the server running Share-<br />

Point Portal Server. The server running SharePoint Portal Server was the limiting<br />

resource in this scenario. The server running SQL Server was 32 percent<br />

busy on average. The best way to scale from this environment is to move to a<br />

load-balanced or highly available medium server farm.<br />

■ The load-balanced farm supported a sustained throughput of 39 operations per<br />

second, with the limiting resource being the two NLB front-end servers running<br />

at 80 percent average CPU. The server running SQL Server was 50 percent busy<br />

on average.<br />

■ The highly available medium server farm with SQL cluster configuration supported<br />

a sustained throughput of 110 operations per second, with the limiting<br />

resource being the two NLB front-end servers running at 80 percent average<br />

CPU consumption. SQL Server (2 × 2.8 GHz) was 35 percent busy on average.<br />

The SQL Server used could support a maximum of four front-end servers, providing<br />

a total of over 200 operations per second. However, a medium server<br />

farm topology does not support more than two front-end servers, so to scale<br />

from this configuration, you must increase the number of processors in your<br />

front-end servers or move to a large server farm configuration.<br />

■ The minimum large farm configuration with a SQL cluster supported a<br />

throughput of about 125 operations per second, with the limiting resource<br />

being the two NLB front-end Web servers running at 80 percent busy on average.<br />

SQL Server (4 × 2.0 GHz) was 25 percent busy. Adding a front-end Web<br />

server would add about 60 operations per second to the total capacity. The<br />

server running SQL Server (4 CPUs) could support a total of six front-end<br />

servers, yielding a total of over 375 operations per second.<br />

■ The search service, running on either the front-end Web servers or on dedicated<br />

servers, was not used heavily with the test workload, which employed<br />

between 10 percent <strong>and</strong> 25 percent search function activity, or 8 to 10 searches<br />

per second. However, search-specific testing showed that a single dedicated<br />

search server can support over 210 search operations per second. The second<br />

search server in the prescribed large server farm configuration is to ensure<br />

availability of the search service if the other server were to fail.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!