The ESXi Server has an advanced CPU scheduler geared towards providing high performance, fairness, and isolation of VMs running on Intel/AMD x86 architectures.
The ESXi CPU scheduler is designed with the following objectives:
- Performance isolation: Multi-VM fairness
- Coscheduling: Illusion that all vCPUs are concurrently online
- Performance: High throughput, low latency, high scalability, and low overhead
- Power efficiency: Saving power without losing performance
- Wide Adoption: Enabling all the optimizations on diverse processor architecture
There can be only one active process per CPU at any given instant; for example, multiple vCPUs can run on the same pCPU, just not in one instance--often, there are more processes than CPUs. Therefore, queuing will occur, and the scheduler will become responsible for controlling the queue, handling priorities, and preempting the use of the CPU.
The main tasks of the CPU scheduler are to choose which world is to be scheduled to a processor. In order to give each world a chance to run, the scheduler dedicates a time slice (also known as the duration in which a world can be executed (usually 10-20 ms, 50 for VMkernel by default)) to each process and then migrates the state of the world between run, wait, co-stop, and ready.
ESXi implements the proportional share-based algorithm. It associates each world with a share of CPU resource across all VMs. This is called entitlement and is calculated from the user-provided resource specifications, such as shares, reservations, and limits.
To step through this recipe, you need a running ESXi Server, a VM that is powered off, and vSphere Web Client. No other prerequisites are required.
Let's get started:
- Open up vSphere Web Client.
- On the home screen, navigate to
Hosts and Clusters. - Expand the left-hand navigation list.
- In the VM inventory, right-click on
virtual machine, and click onEdit Settings. TheVirtual Machine Edit Settingsdialog box appears. - Click on the
VM Optionstab. - Under the
Advancedsection, click onEdit Configuration.
- At the bottom, enter
sched.cpu.vsmpConsolidateasName,TrueforValue, and click onAdd. - The final screen should like the following screenshot. Once you get this, click on
OKto save the setting:
The CPU scheduler uses processor topology information to optimize the placement of vCPUs onto different sockets.
Cores within a single socket typically use a shared last-level cache. The use of a shared last-level cache can improve vCPU performance if the CPU is running memory-intensive workloads.
By default, the CPU scheduler spreads the load across all the sockets in under-committed systems. This improves performance by maximizing the aggregate amount of cache available to the running vCPUs. For such workloads, it can be beneficial to schedule all the vCPUs on the same socket, with a shared last-level cache, even when the ESXi host is under committed. In such scenarios, you can override the default behavior of the spreading vCPUs across packages by including the following configuration option in the VM's VMX configuration file: sched.cpu.vsmpConsolidate=TRUE. However, it is usually better to stick with the default behavior.