Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

CPU usage of an application differs in virtual machines compared to physical machines (2032)

Last Updated: 2/8/2010Categories: Best PracticesTotal Views: 22509Language:
English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Details

This article describes why CPU usage for specific applications differs on ESX 2.x hosted virtual machines when compared to running on physical machines.

Solution

There are a number of factors that contribute to differences in CPU utilization measurements:

When a virtual machine is idle, it may either execute an idle loop or halt the CPU. Executing an idle loop consumes CPU resources on the host while the guest itself appears to be inactive. For more information, see ESX 2.5 reports increased CPU utilization for idle Microsoft Windows Server 2003 SP1 SMP virtual machines (1077) and ESX 2.5 reports increased CPU utilization for idle Microsoft Windows Server 2003 SP1 SMP virtual machines (1730).

The CPU utilization reported by native guest operating system tools like Windows Task Manager is relative to the CPU resources allocated to it by the host. For example, a virtual machine may be limited to 50 percent of a physical CPU by the host; this portion is what the guest operating system considers 100 percent. This differs greatly from an operating system running on a physical machine, which has access to 100 percent of the underlying physical CPU at all times, whether it is needed or not. For detailed information on the challenges of measuring the CPU load from within a virtual machine, please see page 17 of the white paper Timekeeping in VMware Virtual Machines at www.vmware.com/pdf/vmware_timekeeping.pdf.

Virtual machine CPU utilization reported by VMware virtual infrastructure monitoring tools (for example, esxtop) is in the context of physical CPU resources used on the host, not on the guest operating system.

Timer interrupts inside a virtual machine can occur in bursts due to the nature of scheduling multiple virtual machines by the host. This issue is covered in more detail in the white paper ESX Server Architecture and Performance Implications under the section, "Keeping Time in Virtual Machines," at www.vmware.com/pdf/esx2_performance_implications.pdf.

Differences in physical and logical CPUs may create the appearance of extreme differences in utilization. For example, a demanding single-threaded application running on a hyperthreaded physical CPU causes the task manager to report that only 50 percent of the CPU is utilized. However, the same application running on a single non-hyperthreaded or virtual CPU shows up in the task manager at 100 percent utilization, even though the same amount of processing is taking place.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware ESX Server

Related Versions:

VMware ESX Server 2.5.x

VMware ESX Server 2.1.x

VMware ESX Server 2.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant