Time that the virtual machine was ready, but could not get scheduled to run on the physical CPU during last measurement interval Percentage of time that the virtual machine was ready, but could not get scheduled to run on the physical CPU Time the virtual machine was interrupted to perform system services on behalf of itself or other virtual machines Time the virtual machine is ready to run, but is not run due to maxing out its CPU limit setting Percent of time the virtual machine is unable to run because it is contending for access to the physical CPU(s)ĬPU load average over the past 15 minutes, sampled on every 6 secondsĬPU load average over the past 1 minute, sampled on every 6 secondsĬPU load average over the past 5 minutes, sampled on every 6 seconds Total time that the CPU spent in an idle state The amount of CPU resources a virtual machine would use if there were no CPU contention or CPU limitĬPU resource entitlement to CPU demand ratio (in percents)ĬPU resources devoted by the ESX scheduler Time the virtual machine is ready to run, but is unable to run due to co-scheduling constraintsĪmount of CPU resources allocated to the virtual machine or resource pool, based on the total cluster capacity and the resource configuration of the resource hierarchy The number of virtual processors running on the hostĬPU utilization of the corresponding core (if hyper-threading is enabled) as a percentage during the interval (A core is utilized if either or both of its logical CPUs are utilized) The number of virtual processors provisioned to the entity Time the VM vCPU is ready to run, but is unable to run due to co-scheduling constraints The amount of CPU resources a VM would use if there were no CPU contentionĬPU resources devoted by the ESXi scheduler to the virtual machines and resource poolsĬapacity in MHz of the physical CPU coresĬPU usage as a percent during the interval Percent of time the VM is unable to run because it is contending for access to the physical CPU(s) VSphere HA number of failures that can be toleratedĪggregate available memory resources of all the hosts within a cluster Total amount of machine memory of all hosts in the cluster that is available for use for virtual machine memory and overhead memory Total available CPU resources of all hosts within a cluster These performance counters can also be used for performance analysis with, or PowerCLI.įairness of distributed CPU resource allocation

Performance counters can be views for Virtual Machines, Hosts, Clusters, Resource Pools, and other objects by opening Monitor > Performance in the vSphere Client.

This is a list of all available performance metrics that are available in vSphere vCenter Server 7.0.

Cpu usage vs physical memory