Logical Processors

The Logical Processor window allows to determine how much of the physical processor are being used

The grid located at the top of the window shows each individual processor with the following information for each one:

% Hypervisor Run Time This is the percentage of time the Hypervisor is running on an LP or for _Total the average percentage across all LP.  This is similar to % Kernel Run Time in the Processor counter set.
% Guest Run Time This is the percentage of time guest code is running on an LP or for the _Total the average percentage across all LP.  For example if you have 2LP and one VM running CPU tests you might see the value be 95% for LP(0), 0% for LP(1) and 47.5% for the _Total.  For this you can see you VM is running on LP(0).
% Total Run Time This is just a sum of %Guest Run Time + % Hypervisor Runtime. 
% C1 Time C1 is a power saving mode in a CPU.  This counter keeps track of how often the process is able to enter a power saving state when idle.  So %C1 Time is the percentage of time the LP is in the C1 state and for _Total  the average percentage across all LP
% C2 Time The percentage of time the processor spends in the C2 low-power idle state. % C2 Time is a subset of the total processor idle time. C2 is a deeper power state than C1.
% C3 Time The percentage of time the processor spends in the C3 low-power idle state. % C3 Time is a subset of the total processor idle time. C3 is a deeper power state than C2.

By default, the last snapshot is displayed in the grid. Use the slidder (or the arrow buttons) located at the top of the grid to navigate through the collected snapshots. In monitoring, the "Auto-Update" button must be unchecked to be able to navigate through the collected snapshots.

Select one or more processors in the grid (Check box at the left of the grid) to update the graphes located at the bottom of the window. If several processors are selected, the statistics are aggregated.


See also:





Go back to the Learning center:


Copyright © AgileLoad. All rights reserved.
Agile Load testing tool| Contact AgileLoad | Terms of Use | Sitemap