No, it doesn't matter how you mix VMs with different vCPUs counts. Each VM/vCPU is scheduled individually from each other.
As long as you don't overcommit too many (busy) vCPUs on a host you're fine, which obviously applies no matter whether all VMs have the same amount of vCPUs or not.
No, it doesn't matter how you mix VMs with different vCPUs counts. Each VM/vCPU is scheduled individually from each other.
As long as you don't overcommit too many (busy) vCPUs on a host you're fine, which obviously applies no matter whether all VMs have the same amount of vCPUs or not.
Exactly. Virtualization is practically the sole answer to the question above
Stop by my blog if you'd like 🙂 I dabble in vSphere troubleshooting, PowerCLI scripting and NetApp storage - and I share my journeys at http://vmxp.wordpress.com/
Thanks for your responses, I did some digging around meanwhile because there is some kind of myth running in our company about impact when mixing single vCPU VMs and Multiple vCPU VMs and seems to be related to version 2.x of ESX according to these blog articles :
That is correct that was an issue with the CPU scheduler used in ESX 2 hosts - with three that issue was resolved and only has gotten better with each subsequent release of vSphere
If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
