VMware vCPU Overcommit Calculator

Check your vCPU to physical CPU ratio against workload-appropriate limits and read it against observed CPU ready time.

About VMware vCPU Overcommit Calculator

The ratio itself is simple division, but it is only half the picture: ESXi will happily schedule 20:1 and the scheduler decides whether that hurts. CPU ready time is the empirical answer — under 3% the ratio is fine whatever it says, and above 5% it is too high even if the arithmetic looks conservative. A ratio chosen from a spreadsheet without checking ready time either wastes hardware or produces mystery latency that application owners blame on the storage array.

Formula

VMware vCPU Overcommit

ratio = total allocated vCPUs ÷ (hosts × cores × threads per core); the ratio is then compared with the profile ceiling and cross-checked against CPU ready time.

threads per core: 2 when hyper-threading is counted, otherwise 1
profile ceiling: Ratio the workload class tolerates before latency suffers
ready time: Percentage of time a vCPU is runnable but waiting for a physical core

Worked example

With the default values below, VMware vCPU Overcommit Calculator returns Current vCPU to pCPU Ratio of 3.39. Change any input above and every figure here is recalculated in your browser.

Inputs used

Hosts in clusteraccepts 1–96 hosts: 4 hosts
Physical cores per hostaccepts 1–512 cores: 24 cores
Count hyper-threads as logical CPUs: Yes
Total vCPUs allocatedaccepts 1–100,000 vCPU: 650 vCPU
Workload profileone of Latency-sensitive (1:1), Database or SAP (2:1), General purpose (4:1), VDI (6:1), Test and development (8:1): General purpose (4:1)
Observed CPU ready timeaccepts 0–60 %: 3.2 %

Results

Current vCPU to pCPU Ratio: 3.39 :1
Logical CPUs Available: 192 logical CPUs
Recommended Ceiling: 4.0 :1
vCPU Headroom to Ceiling: 118 vCPU
Ready Time Reading: Watch — approaching the 5% threshold
Overcommit Verdict: Comfortably within the ceiling for this profile

Step by step

1Values used
2VMware vCPU Overcommit
3Current vCPU to pCPU Ratio= 3.39 :1
4Logical CPUs Available= 192 logical CPUs
5Recommended Ceiling= 4.0 :1
6vCPU Headroom to Ceiling= 118 vCPU
7Ready Time Reading= Watch — approaching the 5% threshold
8Overcommit Verdict= Comfortably within the ceiling for this profile

Assumptions and limits

The result is derived only from the 6 inputs listed above. Anything not among them is not part of the calculation.
In particular, this calculator does not take inflation, tax or compounding frequency into account.
Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.

How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.

Frequently Asked Questions

How is VMware vCPU Overcommit calculated?

ratio = total allocated vCPUs ÷ (hosts × cores × threads per core); the ratio is then compared with the profile ceiling and cross-checked against CPU ready time. The ratio itself is simple division, but it is only half the picture: ESXi will happily schedule 20:1 and the scheduler decides whether that hurts. CPU ready time is the empirical answer — under 3% the ratio is fine whatever it says, and above 5% it is too high even if the arithmetic looks conservative.

Why does VMware vCPU Overcommit matter?

A ratio chosen from a spreadsheet without checking ready time either wastes hardware or produces mystery latency that application owners blame on the storage array.

What values do I need to enter?

This calculator takes 6 inputs: Hosts in cluster, Physical cores per host, Count hyper-threads as logical CPUs, Total vCPUs allocated, Workload profile, Observed CPU ready time. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Is a 1:1 ratio ever justified?

Yes — for latency-sensitive VMs such as trading engines, real-time telco workloads or licensed database cores, where you also pin CPU affinity and set full reservations. Everywhere else 1:1 wastes most of the hardware you bought.