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 10: Performance Monitoring in <strong>Microsoft</strong> Office SharePoint Portal Server 2003 241<br />

Separating the Effects of Searching from Other Front-End Traffic When deciding<br />

to scale out front-end Web/search servers, you must determine how much of the<br />

CPU load is the result of search operations. As a rule of thumb, when the query rate<br />

counter exceeds the indicated threshold <strong>and</strong> search operations are consuming about<br />

40 to 50 percent of the overall server capacity, you should consider scaling out to a<br />

large server farm. If the query rate is below the threshold but percent processor time<br />

is exceeding the threshold, front-end Web traffic is bringing the server to capacity<br />

<strong>and</strong> you should consider adding an additional front-end Web/search server to the<br />

medium server farm.<br />

Be sure to take into consideration the impact of extensive front-end traffic to<br />

Windows SharePoint Services sites. If some of your Windows SharePoint Services<br />

sites are generating significant front-end traffic, you might want to scale out one or<br />

more of those sites to a separate server farm, as discussed in the “Dedicated Windows<br />

SharePoint Services Server Farm” section later in this chapter.<br />

Other Factors That Influence Search Performance Keep in mind that other factors<br />

can cause heavy search loads—for example, a large content index (which can<br />

slow down search performance) or heavy search query executions against a single<br />

portal in a shared services farm. Make sure that user expectations for search performance<br />

are realistic for your environment. Your customer’s requirements for search<br />

response times, including commitments to service-level objectives that define specific<br />

response times for searches, can necessitate adding a server before the thresholds<br />

have been exceeded.<br />

Dedicated Search Servers—Large Server Farm<br />

Table 10-4 lists the most important counters for evaluating the performance of a dedicated<br />

search server in a large server farm.<br />

Table 10-4 Performance Counters for Dedicated Search Servers—Large Server Farm<br />

Object Counter Threshold Description<br />

Processor Percent processor<br />

time_total<br />

80 to 85 percent averaged<br />

over three intervals.<br />

The total percentage of processor<br />

usage for a server.<br />

Search Query rate 20 per second. The number of queries posted to<br />

the server per second. Keep in<br />

mind this counter should be<br />

watched on the dedicated search<br />

servers.<br />

Search Succeeded<br />

queries<br />

This counter should be used<br />

mostly for troubleshooting<br />

search problems.<br />

The number of queries that produce<br />

successful searches; monitor<br />

this counter along with the failed<br />

queries counter if you need to<br />

troubleshoot search problems.

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

Saved successfully!

Ooh no, something went wrong!