Windows Server Performance Analysis
1. Collect Data
I then use logman to create my collection
logman create counter MyCollection -s %computername% -cf counterstxt
I then start the collection like this:
logman MyCollection start
Once I have collected a representative sample I stop the collection as follows:
logman MyCollection stop
By default on Vista and Windows 2008 servers, your performance monitor counters will be stored in %systemdrive%\PerfLogs\Admin and will be named after your collection name (in our case they will be called MyCollection.blg (blg is the extension for perfmon counters). On Windows 2000, 2003 and XP machines they will be stored by default in %systemdrive%\PerfLogs.
2. Controlling Performance Monitoring Overhead
When you select a counter in any view, the performance tools collect data for all counters of that object, but display only the one you select. This causes only minimal overhead, because most of the tools' overhead results from the display. You can control monitoring overhead in the following ways:
Use logs instead of displaying a graph. The user interface is more costly in terms of performance.
Limit the use of costly counters; this increases monitoring overhead. For information about costly counters, see the Performance Counter Reference on the Microsoft ® Windows ® 2000 Resource Kit companion CD.
Lengthen collection intervals if possible. In general, 600-second (10-minute) intervals are sufficient for ordinary monitoring.
Collect data during peak activity rather than over an extended interval.
Reduce the number of objects monitored unless these are critical to your analysis.
Put the log file on a disk that you are not monitoring.
Check the log file size when logging multiple servers to a single computer to see how much space the data is taking up.
Limit to brief periods the trace logs that are monitoring page faults or file I/O. Prolonged trace logging strains system performance.
Avoid configuring System Monitor reports to display nondefault data. If you choose nondefault data (the defaults are Average value for logs; Last value for graphs) in the Report view, the statistic is calculated at each sample interval. This incurs some additional performance overhead.
From: http://technet.microsoft.com/en-us/library/cc938553.aspx
I then use logman to create my collection
logman create counter MyCollection -s %computername% -cf counterstxt
I then start the collection like this:
logman MyCollection start
Once I have collected a representative sample I stop the collection as follows:
logman MyCollection stop
By default on Vista and Windows 2008 servers, your performance monitor counters will be stored in %systemdrive%\PerfLogs\Admin and will be named after your collection name (in our case they will be called MyCollection.blg (blg is the extension for perfmon counters). On Windows 2000, 2003 and XP machines they will be stored by default in %systemdrive%\PerfLogs.
2. Controlling Performance Monitoring Overhead
When you select a counter in any view, the performance tools collect data for all counters of that object, but display only the one you select. This causes only minimal overhead, because most of the tools' overhead results from the display. You can control monitoring overhead in the following ways:
Use logs instead of displaying a graph. The user interface is more costly in terms of performance.
Limit the use of costly counters; this increases monitoring overhead. For information about costly counters, see the Performance Counter Reference on the Microsoft ® Windows ® 2000 Resource Kit companion CD.
Lengthen collection intervals if possible. In general, 600-second (10-minute) intervals are sufficient for ordinary monitoring.
Collect data during peak activity rather than over an extended interval.
Reduce the number of objects monitored unless these are critical to your analysis.
Put the log file on a disk that you are not monitoring.
Check the log file size when logging multiple servers to a single computer to see how much space the data is taking up.
Limit to brief periods the trace logs that are monitoring page faults or file I/O. Prolonged trace logging strains system performance.
Avoid configuring System Monitor reports to display nondefault data. If you choose nondefault data (the defaults are Average value for logs; Last value for graphs) in the Report view, the statistic is calculated at each sample interval. This incurs some additional performance overhead.
From: http://technet.microsoft.com/en-us/library/cc938553.aspx
posted by oh_csharp at
9:06 AM
0 Comments:
Post a Comment
<< Home