CPU Oversubscription Calculator

The vCPU-to-core ratio of a host, or the vCPU budget for a target ratio.

What does this calculator do?

CPU oversubscription is the practice of allocating more virtual CPUs than the host has physical cores, on the reasonable assumption that not every VM is busy at once. The ratio expresses how far you have gone: 4:1 means four vCPU allocated per physical core. This calculator works in both directions — measure the ratio of an existing host from its allocated vCPU, or turn a target ratio into the vCPU budget you may allocate. The arithmetic is exact; whether a given ratio is safe is a workload question, not a mathematical one. Everything is computed in your browser from the values you type. Nothing is looked up on the network — there is no ping, no DNS query, no WHOIS and no geolocation.

Formula

One division, or the same relationship rearranged.

ratio = allocatedVcpu ÷ physicalCores
plannedVcpu = physicalCores × targetRatio

How to use it

Choose the mode and the form shows the field it needs. Count physical cores, not hyper-threads, unless your capacity standard says otherwise — counting threads silently doubles your apparent ratio. In ratio mode, sum the vCPU of every powered-on VM on the host. In planned mode, enter the ratio your standard permits for this workload class and the result is the total vCPU you may allocate.

Worked example

Ratio mode: 128 vCPU allocated on a 32-core host gives 128 ÷ 32 = 4, a 4:1 ratio — four vCPU per physical core. Planned mode: the same 32-core host with a 4:1 target allows 32 × 4 = 128 vCPU in total, which is 32 VMs of 4 vCPU each.

Formula version1.0.0
Formularatio = allocatedVcpu ÷ physicalCores plannedVcpu = physicalCores × targetRatio
Precision3 decimals

Frequently asked questions

What ratio is too high?

The symptom to watch is CPU ready time — how long a VM waits for a physical core. Ratios that are fine for idle test VMs cause visible latency for databases and desktops. Raise the ratio only while ready time stays low on your own hosts.

Should hyper-threads count as cores?

Most capacity standards count physical cores and treat simultaneous multithreading as headroom, because two threads on one core do not deliver two cores of work. Counting threads makes a 4:1 ratio look like 2:1 and hides real contention.

Does a big VM count differently from several small ones?

The ratio does not distinguish them, but scheduling does. Wide VMs need many cores free simultaneously, so a host full of large VMs suffers more under the same ratio than one running many small ones.

Sources

Related calculators

Last updated: 2026-08-10 · v1.0.0 · Report an error