_VMware: VROOM!: ESX scheduler support for SMP VMs: co-scheduling and more:
- When do I decide to configure multiple vCPUs for a VM?
- What are the overheads of using multiprocessor VMs? What would I lose by over provisioning vCPUs for VMs?
- Does the ESX scheduler (co-schedule) all of the vCPUs belonging to a VM together?
- Why is co-scheduling necessary and important?
- How does ESX scheduler deal with certain vCPUs belonging to a VM idling while others actively perform work? Do the idle vCPUs unnecessarily burn CPU?
(Via VROOM!.)_
Some very useful information (with a good dose of common sense) concerning the optimal use of multiple VCPU configurations. Very interesting points regarding the changes in the coscheduling between ESX 2.x and 3.x.
This kind of stuff is really important so that we don’t continue to base architectural decisions on outdated information.