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.

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:

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.