Originally Posted by vincecmic
I am also getting alot of emails regarding the "processor load is too high" message on Windows VM guests.
Please help me out with the solution.
Thanks for your help
Have you read the document from Wikipedia I've mentioned on my previous post?
A first step is to understand, when talking about performance monitoring techniques, that "% Processor Time" and "Processor Queue Length" are two different things. Often people mistake "Processor Queue Lenght" with "% Processor Time" has I think the developer that made the Zabbix Windows Template and named it "system.cpu.load"... Also those metrics were developed 20 years ago for Windows NT
and for physical machines not virtual
(VMWare or Hyper-V).
The "% Processor Time" counters in Windows are measurements derived using a sampling technique. The OS Scheduler samples the state of the CPU once per system clock tick, driven by a high priority timer-based interrupt.
The "System\Processor Queue Length" counter in Perfmon is an instantaneous counter
that reflects the current number of Ready threads waiting in the OS Scheduler queue.
From Microsoft's Technet (http://technet.microsoft.com/en-us/l.../cc940375.aspx
) you can see the usage of "% Processor Time" and "System\Processor Queue Length" combined in order to find saturated processors. There is also a note at the end with reference values for multiprocessor systems (also physical servers).
On a virtual environment you can't use the same trigger values because virtual processors and queuing are handled differently than physical one's. The physical processor queues are used for several virtual processors and that messes up the values you use as reference for Zabbix triggers.
If I remember right the value set for the trigger was 5 and if you read the note I've mentioned, on a system with high CPU activity the expected range of processor queue length is 4 to 12 so the trigger must be set higher.
This post is getting veeerrrryyyy biiiigggg and I'm expecting a remote assist from a software provider at any minute, so I must stop for now but...
You can make a first experience. Open a perfmon on two windows boxes (physical and virtual) and add the counters for "% Processor Time" and "System\Processor Queue Length". Let it run for a while and compare the graphs with the ones on the Technet article.
I'll be back later...