Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Windows Virtual Machines with Latency-Sensitive I/O Workloads Can Slow Down in Four-Way SMP Configurations (2231)

Last Updated: 7/7/2020Categories: TroubleshootingTotal Views: 5154Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Details

Under certain conditions, four-way Windows virtual machines, and to a lesser extent, two-way Windows virtual machines may slow down compared to the same workload run in a uniprocessor virtual machine. The virtual machine also exhibits an increased amount of idle time. This can happen in cases where there is not sufficient work to keep the processors busy and when the workload has a low rate of external interrupts.

ESX Server 3.0.x includes a specialized virtual machine idle loop handler, which controls the number of microseconds a Windows SMP virtual machine spins in its idle loop before ESX Server halts the virtual machine. For ESX Server 3.0.x, the default value is 100. For some workloads, the delay caused by halting and then resuming the VCPUs causes a measurable slowdown as the number of VCPUs is increased.

Solution

Try setting the virtual machine configuration option monitor.idleLoopSpinUS = <n> to increase the amount of time spent spinning in the idle loop (values greater than 100 and less than 4000 are recommended, for example 1000 or 2000). For example:

Schedule some down time.

Power off the virtual machine.

Add
monitor.idleLoopSpinUS = 1000
to the configuration file of the virtual machine (.vmx extension).
Note: For instructions on how to edit the .vmx file, see Tips for editing a .vmx file

Power on the virtual machine.

You can set monitor.idleLoopSpinUS = -1 to turn off the idle loop handler and allow the virtual machine to spin in its idle loop as determined by the guest operating system. However, VMware doesn't recommend using monitor.idleLoopSpinUS = -1 unless necessary, because it can cause the guest operating system to spin unnecessarily in its idle loop, resulting in unnecessary host CPU utilization possibly diverting CPU resources from other virtual machines. You can also use a one-way or two-way virtual machine.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

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 3.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