Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Linux has a notion of Load Average which is defined as:

System load averages is the average number of processes that are either in a runnable or uninterruptable state. A process in a runnable state is either using the CPU or waiting to use the CPU. A process in uninterruptable state is waiting for some I/O access, eg waiting for disk. The averages are taken over the three time intervals. Load averages are not normalized for the number of CPUs in a system, so a load average of 1 means a single CPU system is loaded all the time while on a 4 CPU system it means it was idle 75% of the time.

What is the closest equivalent available via WMI? Fundamentally are there differences between the two OSes which determinate how such a performance metric should be measured? What are the differences?

share|improve this question
up vote 8 down vote accepted

The Process Queue Length count from the System performance counter object is:

Processor Queue Length is the number of threads in the processor queue[...]

This value is available in WMI via Win32_PerfFormattedData_PerfOS_System.

share|improve this answer
Digging in a bit this answer… seems to give a good view of the differences between the OSes. – leonigmig Nov 8 '11 at 10:10

I don't know of any such measure of overall work-demand, it's just percent-CPU with some breakdown in the kinds of CPU demanded. This does make it hard to figure out just how overloaded a machine is. When a Linux system is reporting a Load Average of 63 and the Windows system is reporting 100% CPU... well, they're both running flat out, but that's about all you can tell about the Windows system.

share|improve this answer

I'm not sure that there is anything in windows that would be equivalent, and I'm not sure it would mean anything if there were there. From the description I can't see how a process would fail to be included as even a hung or suspended process would get CPU time allocated. Additionally it's more relevant to look at threads and runnable threads rather than processes under windows in order to determine any notion of load by the definition provided.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.