Applications Systems

esxtop rdy is showing higher value than the VMAN appliance chart variable CPU Percent Ready

This article explains why the VMAN appliance chart/report variable for CPU Ready percent is showing a lower value than the one in esxtop %rdy value. esxtop is a legacy VMware tool that VM administrators use to monitor the VM environment (Hosts and VM's) utilization statistics in real time.

First published date

10/16/2018 6:56 PM

Last published date

5/6/2019 2:26 PM

Overview

This article explains why the VMAN appliance chart/reports variable for CPU Ready percent is showing a lower/higher value than the esxtop %rdy value.

esxtop is a legacy VMware tool that VM administrators use to monitor the VM environment (Hosts and VM's) utilization statistics in real time.

Product section

Virtualization Manager

Cause

NA

Resolution

The following image shows the esxtop %rdy value for ESX host phlprwssqls02 is at 42.58%:


Since the ESX host is added under a vCenter and the vCenter is added as the datasource in VMAN i.e VMAN gets the data of the ESX host from the vCenter when polled via Vcenter or ESXi hosts directly it will show the same or close to its realtime value. See the following:


When compared to VMAN by creating a chart/Out of the box cpu ready reports that will show the CPU ready percent of the ESX host. It will show a lower value. See the following:


Explanation: 

  • This is not an issue.  
  • vCenter and esxtop show "%rdy per VM" as summation of "%rdy per vCPU".
  • This makes sense when you consider "%rdy per VM" = number of CPU cycles lost because or Ready state.
  • Generally, "%rdy per vCPU" > 5 % tells admin that he should look at the issue, "%rdy per vCPU" > 10 % is considered to be critical and admin should definitely fix this.
  • "%rdy per VM" is just summation, to show admin that he is losing efficiency a lot (that is, 10 % rdy per vCPU on VM with 8 vCPUs shows 80 % rdy per VM).
  • The disadvantage of this is that %rdy per VM can possibly go over 100 %.

VMAN respects the fact that values in % should never go over 100 %. That is why VMAN shows "CPU Ready % per VM" as average of "CPU Ready % per vCPU". This makes sense as admin should take attention to VMs with CPU Ready % per VM on 5 % (warning) or 10 % (critical).

Summary: 

  • vCenter and esxtop show "%rdy per VM" as SUM of "%rdy per vCPU".
  • VMAN shows "%rdy per VM" as AVG of "%rdy per vCPU".
  • "VMAN %rdy per VM" should equal to "esxtop %rdy per VM" / "number of vCPUs on VM".
  • "%rdy per vCPU" values should be equal in VMAN and in vCenter.

Disclaimer: Please note, any content posted here is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.