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.

Chapter 10: Performance Monitoring in <strong>Microsoft</strong> Office SharePoint Portal Server 2003 239<br />

SharePoint Portal Server Counters<br />

Each type of server—index, search, <strong>and</strong> front-end Web—has performance counters<br />

specific to its function in the server farm. This section lists the counters that should be<br />

analyzed for each server type to determine how <strong>and</strong> when to scale the server farm.<br />

Front-End Web Servers—Large Server Farm<br />

Analyze the counters in Table 10-2 to determine when to add a new dedicated<br />

front-end Web server to a large server farm. When the counters continuously<br />

approach or exceed any of the thresholds in Table 10-2, you should consider adding<br />

another dedicated front-end Web server to the server farm. However, you<br />

should also check the general counters in Table 10-1 to better underst<strong>and</strong> the<br />

server’s performance.<br />

Table 10-2 Performance Counters for Dedicated Front-End Web Servers<br />

Object Counter Threshold Description<br />

Processor Percent processor<br />

time_total<br />

ASP.NET<br />

applications<br />

Requests per<br />

second_total<br />

Web service Get requests per<br />

second_total, individual<br />

portal, or<br />

IIS Virtual root<br />

80 to 85 percent averaged<br />

over three intervals.<br />

Through ongoing monitoring,<br />

trends begin to emerge that<br />

equate requests per second<br />

with CPU consumption.<br />

Through ongoing monitoring,<br />

trends begin to emerge that<br />

equate get requests per second<br />

with CPU consumption.<br />

The total percentage of processor<br />

usage for a server.<br />

The number of requests executed<br />

per second; this roughly equates<br />

to the number of HTTP pages per<br />

second.<br />

Generally speaking, this is the rate<br />

at which clients are requesting<br />

information from the front-end<br />

Web servers.<br />

Leading Indicators for Front-End Web Servers<br />

The counter percent processor time is the leading indicator of front-end Web<br />

server performance. You should sample percent processor time every 15 minutes; if<br />

it exceeds the indicated threshold on average, consider adding an additional frontend<br />

Web server. If your customer has very high performance expectations, you<br />

might need to establish a lower average threshold.<br />

The value that requests per second reaches while percent processor time is at<br />

the threshold indicates the approximate maximum throughput for the server. Adding<br />

a front-end Web server should add this amount of capacity to the server farm.<br />

Impact of Windows SharePoint Services Sites<br />

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

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

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

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

Windows SharePoint Services Server Farm” section later in this chapter.

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

Saved successfully!

Ooh no, something went wrong!