Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The first data point that is in a Performance Monitor log .csv file may be a larger number than expected on Windows Server 2003


View products that this article applies to.

Symptoms

You collect Performance Monitor data on a Windows Server 2003 machine. When the data is collected in the comma-separated value (.csv) format, the first data point that is collected may be a larger number than expected. This behavior occurs if the counter being monitored uses delta time, and if the log is set to start and to stop automatically. For example, the delta time is the�%Processor Time time.

↑ Back to the top


Cause

This issue occurs because the first data point is taken immediately.

When a log is stopped and then started automatically, the time between the last data point that is in the previous log and the first data point that is in the new log is very small. This behavior causes a very small divisor for the values that measure delta time. Therefore, the value of the resultant is larger than expected.

For example, the value of the resultant is as follows:
"date time","25.0000959987712157" <--- 25%, even though the CPU was idle
"date time","0.31377598366740811"
"date time","0.31377598366740811"

↑ Back to the top


Workaround

To work around this issue, do one of the following:
  • Collect data by using the binary (.blg) file format.
  • Ignore all data values that seem too large to be accurate.

↑ Back to the top


Keywords: KB983254, kbprb, kbsurveynew, kbexpertiseinter, kbtshoot

↑ Back to the top

Article Info
Article ID : 983254
Revision : 3
Created on : 9/11/2011
Published on : 9/11/2011
Exists online : False
Views : 241