Monitoring W2K performance
Peter Parsons
Published: 04 Dec 2002 15:47 GMT
Measuring systems' performance on a network is one way for a company to protect itself from unacceptable levels of downtime, should any critical components of that network go belly-up. Monitoring performance creates early warning systems for an administrator; therefore its implementation should be viewed as an integral part of network administrative duties.
Windows 2000 ships with advanced performance tools to help you measure and report what your systems are doing. These tools contain numerous types of counters that measure different aspects of performance. I'll examine which areas of performance are worth your attention and how to set up basic benchmark performance counters in Windows 2000 to help you measure the most crucial elements of a system's performance.
What do you monitor?
On a typical server, there are four basic counters that are critical to the smooth running of that machine. In no particular order, they are:
- Memory: Pages/sec.
- Processor: \% Processor Time
- Physical disk: \% Disk Time
- Network: Bytes Total/Sec
Obviously, if you're going to monitor performance, you need to be able to compare any abnormalities with normality. This is why you need to use these four counters to establish a performance benchmark on every system.
Remember that because all computers do different jobs and many contain different hardware components, benchmarks will vary from system to system. Also, if you change a system, you should recreate the benchmark data to reflect those changes.
To establish a benchmark, it is worth monitoring the four basic counters over a period of time representative of typical daily usage. The period should include the busiest and slowest times of day. To start, you may want to set a benchmark over 24 or 48 hours. Make sure you monitor Server A's counters from another machine, because if you monitor Server A from Server A, you'll compromise its performance and set a false benchmark. Note also that changes in average values can indicate bottlenecks in a system. Now, what do these four basic counters measure?
Network
Bytes Total/sec is the rate at which bytes are sent and received on the network interface. This will vary depending on the speed of the network adapter and congestion on the network.
Processor
% Processor Time is the percentage of the sample interval the CPU spends doing useful work. This counter was designed as a primary indicator of processor activity. It displays the average percentage of busy time observed during the sample interval.
Physical disk
% Disk Time is the percentage of elapsed time that the selected disk drive is busy servicing read or write requests. The higher the average is, the slower the performance will be.
Memory
Pages/sec is the number of pages read from or written to disk to resolve page faults. A page fault is when a process needs to retrieve code from the physical disk because it is not available in memory. This counter was designed as a primary indicator of the kinds of faults that cause system delays. The performance of any system is affected by the relationship between the amount of physical memory and the size of the paging file, which is where memory swaps happen.
As a rule of thumb, the page file size should be set to at least twice the amount of memory. So if you have 512 MB RAM in a system, the page file size (minimum and maximum) should be set at 1024 MB. This will allow the entire contents of memory to be written to a 'core dump' if a crash occurs. The core dump can then be used to debug the cause of the crash. By setting the min/max values as the same, you avoid making the server work more by having to recalculate the page file size. Equally, if you can stripe a page file across physical disks, this will help performance.
Previous
Did you find this article useful?
59 out of 143 people found this useful
- Share this article:
