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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

218 Part III: Planning <strong>and</strong> Deployment<br />

In the common medium server farm, each function is implemented on redundant<br />

servers, with the exception of the indexing <strong>and</strong> job server functions. (There can<br />

be only one index <strong>and</strong> job server per farm.) Even the failure of the index <strong>and</strong> job<br />

server does not immediately affect availability because the search services are still<br />

available to end users. However, no indexing of new content is possible until the<br />

index <strong>and</strong> job server becomes available.<br />

In the medium server farm solution, the front-end Web servers also host the<br />

search components for the farm. Consequently, the performance of the front-end<br />

Web servers is predicated on their ability to respond to end-users’ requests to serve<br />

pages <strong>and</strong> to respond to search queries.<br />

You can scale a base-line medium server farm by using one of the following<br />

two methods:<br />

■ Adding a front-end Web <strong>and</strong> search server to the Network Load Balancing cluster,<br />

thereby increasing the capacity <strong>and</strong> availability<br />

Note In a medium server farm, you cannot add dedicated search servers,<br />

nor can you add index <strong>and</strong> job servers. To add such servers, you must<br />

deploy the large server farm. However, you can scale from a medium server<br />

farm to a large server farm after initial deployment.<br />

■ Deploying the medium server farm with a separate dedicated Windows Share-<br />

Point Services farm to host SharePoint Portal Services sites<br />

The five-server medium-server farm configuration was tested by applying a<br />

typical usage workload. This workload contains a mix of typical user functions as<br />

might be used on each of the four main types of portal sites or websites: Corporate,<br />

Divisional, Team Sites, <strong>and</strong> My Sites. This workload <strong>and</strong> the results obtained with it<br />

are considered to be representative of a majority of users <strong>and</strong> business usage. If a<br />

specific customer’s workload differs substantially from the workload used, results<br />

<strong>and</strong> supported throughput for the various functions will vary from those presented<br />

here. Testing will give information for how to take such workload differences into<br />

consideration <strong>and</strong> how to estimate expected performance.<br />

The tested highly available medium server farm with a SQL cluster (the configuration<br />

for which was stated previously in this chapter) provided a sustained<br />

throughput rate of 110 operations per second, where an operation corresponds to a<br />

portal function—for example browse, search, or open document—at an average<br />

CPU consumption of 80 percent on each of the 2 Network Load Balancing (NLB)<br />

Web front-end servers. The average CPU consumption of the active computer running<br />

SQL Server was approximately 35 percent (2 × 2.8 GHz CPUs). This indicates a<br />

4 to 1 ratio between front-end Web server processors <strong>and</strong> SQL Server processors. A

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

Saved successfully!

Ooh no, something went wrong!