Performance Monitor Windows save log
Part 2 – Performance Monitor Demystified
When considering the different tools that are available as part of the Windows Server 2008 operating system that will allow you to review and analyze system performance, the Windows Reliability and Performance Monitor can be leveraged by systems administrator to gather baseline information and to perform server tune ups. In this series of articles we will review the most common uses of the tool and break down some of the tool’s major functions.
Part 1 – Introduction to the Reliability and Performance Monitor took an overview look at the tool and the basic elements of function to get you familiar with the interface and some of the initial features and default settings.
In this segment, Part 2 – Reliability and Performance Monitor – Performance Monitor Demystified, I will go over some of the features and functions of the Performance Monitor part of the tool as well as some best practices with respect to collecting and working with Performance Logs.
What Can You Do With The Performance Monitor?
The Performance Monitor section of the Reliability and Performance Monitor tool can be used to view live performance data as a system is in use. It can also be set up to collect log files over a designated period of time so as to review snapshots of system performance for a historical reference in graphical or report format.
This allows you to have a known baseline for a system if a capture is made during first system build or around the time of initial deployment of a system into a production scenario. By having this baseline capture, you can use it to review against system performance results in the future when there are issues with system response time or if you are doing a capacity review of a server in a given role (e.g. Domain Controller, Database Server, etc).
In most cases, as the systems administrator of a newly configured system, you would want to have a baseline of corresponding performance counters that might be relative for the system’s intended workload.
While you might want to collect many of the base counters like Logical Disk, CPU, Network Interface (etc), you might choose to pick from system specific ones as well. If a system is being put together to be a print server you might want to collect information relative to that role (Print Queue) so that you would have the original baseline for the system.
[NOTES FROM THE FIELD] – Server roles are not always sole designations any more as they used to be. Many systems are configured for dual or multipurpose use. When you are collecting baseline data to be saved as a Data Collector Set you’ll need to decide beforehand what you want to use as a base standard for all systems and then add custom counters for given server roles.
You might also like
Senate panel OKs $51 billion for Commerce, Justice, Science — FCW.com
One sticking point is the House's desire to limit funding for the National Strategy for Trusted Identities in Cyberspace, a plan designed to come up with a new system for managing identities online.