#1 Global Leader in Data Protection & Ransomware Recovery

Reported CPU Usage Values Differ in vCenter and Veeam ONE

KB ID: 1013
Product: Veeam ONE
Published: 2011-07-14
Last Modified: 2023-12-13
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

The reported maximum, minimum, and average CPU usage values do not match between the vCenter and Veeam ONE. 

Cause

How the Values Are Calculated in vSphere Client

VMware calculates these values with Hyperthreading Technology enabled.

The VMware vSphere client shows that “Hyperthreading” is in the “Active” state under the “General” section on the Summary tab for the ESX(i) host within the virtual infrastructure:

User-added image

As a result, the “Advanced” performance page for this host shows total values for all processors but with the Hyperthreading feature enabled.

Once all object are selected under the Chart Option window, the CPU Usage is displayed for all virtual CPUs and the ESX(i) host itself. Summing up the average values of each virtual CPU and then dividing by the number of virtual CPUs produces a value approximately two times smaller than the TOTAL CPU Usage value for the host.

 

How the Values Are Calculated in Veeam ONE

Veeam ONE calculates the total CPU Usage without using VMware’s “Total CPU Usage for entire host with Hyperthreading enabled” option. It takes each CPU's Usage and then performs calculations as described above. Thus, in Veeam Monitor, the Total CPU Usage value is two times smaller than CPU Usage for the entire host on VMware’s graphs.

Solution

No solution required as this is the expected behavior.

More Information

If you have any questions or problems, please contact Veeam Support.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.