Microsoft Sharepoint Products and Technologies Resource Kit eBook

Chapter 10: Performance Monitoring in Microsoft Office SharePoint Portal Server 2003 269
Indirect Monitoring
Summary
Table 10-15 Performance Monitoring of Custom Web Parts (continued)
Type Information Sampling Frequency
All system processes CPU usage Every two hours
Virtual bytes Every two hours
Private bytes Every two hours
Pool paged bytes Every two hours
Pool nonpaged bytes Every two hours
Working set Every two hours
Thread count Every two hours
Note For an explanation of specific performance counters, refer to the
Windows Server 2003 Help and Support Center. You can access the Windows
Server 2003 Help and Support Center by pressing the F1 key.
Monitoring the applications that directly use or access your portal provides an enduser
view of the responsiveness and reliability of the system. Indirect monitoring
provides a better picture of system response time to client requests, especially in
environments that are geographically disparate. Indirect monitoring provides an
accurate view of application performance and effectiveness.
There are third-party solutions that run scripts to simulate client sample loads
from different locations at specific intervals. You can also use free tools and utilities,
such as HTTPPing, to achieve the same goal. For more information about HTTPPing,
visit the MSDN website at http://msdn.microsoft.com, and search for “HTTPPing.”
In this chapter, we have outlined some methods and counters you’ll need to use to
effectively monitor SharePoint Portal Server 2003. In the next chapter, we’ll outline
how to use Microsoft Operations Manager to streamline performance monitoring of
your servers.