Chapter 16. Comprehensive Performance Analysis and Logging

Microsoft Windows Server 2003 provides many tools to help you track performance. In the previous chapter, we looked at tuning performance through configuration settings; using Task Manager to track running processes, users, and network utilization; and using the event logs to track important occurrences recorded by the operating system. Although these tools are excellent and do their jobs well, you might need to dig deeper to establish comprehensive performance baselines, diagnose complex system problems, and optimize system performance.

The key comprehensive monitoring and optimization tools available include the following:

  • System Monitor System Monitor can be used to track and display performance information in real time. It gathers information on any performance parameters you've configured for monitoring and presents it using a graphical display.

  • Performance Logs And Alerts Performance logs can be considered to be the logging counterpart to System Monitor. By using performance logs, you can record performance information in real time and store it in a log so that it can be analyzed later. Performance alerts can be used to notify users when certain events occur or when certain performance thresholds are reached. For example, you could configure a performance alert that lets you know when the C drive is running low on free space or the central processing unit (CPU) is operating at 95 percent or more of capacity.

Before discussing each of these tools in turn, let's look at how you can establish performance baselines.

Establishing Performance Baselines

One of the key reasons for tracking performance information is to establish a baseline for a computer that allows you to compare past performance with current performance. There are several types of baselines you can use, including the following:

  • Postinstallation baselines A postinstallation baseline is a performance level that is meant to represent the way a computer performs after installing all the system components, services, and applications that will be used on the system.

  • Typical usage baselines A typical usage baseline is a performance level that is meant to represent average usage conditions and serve as a starting point against which you can measure future performance.

  • Test baselines A test baseline is a performance level that you use during testing of a system. In the test lab, you might want to simulate peak usage loads and test how the system performs under these conditions.

Although it is important to obtain postinstallation and typical usage baseline values, the more important of the two is the typical usage baseline. This is the baseline you get when you simulate user loads or when users actually start working with a server. Ideally, it represents typical or average loads. Once you have a typical usage baseline, you can gather information in the future to try to determine how resource usage has changed and how the computer is performing comparatively.

To be able to establish a baseline, you must collect a representative set of performance statistics. By that I mean collect the data that you actually need to determine resource usage and performance in future scenarios. If possible, you should also collect several data samples at the same time each day over a period of several days. This will give you a more meaningful data sample.

You must work to keep the baseline in sync with how the server is used. As you install new components, services, and applications, you must establish new baselines. This ensures that future comparisons with the baseline are accurate and that they use the most current system configuration to determine how resource usage has changed and how the computer is performing comparatively.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset