Isvara
·visits
Tools/07 · Capacity Planner

How many VMs fit on a host?

Set the host and the class mix, and aim for 90 to 110% on the binding model.

Fits on this host
101% · on target
11.9VMs
of this mix fit before Allocation CPU, the binding model, reaches 100%. You planned 12.
Allocation CPU by class
0100%
Gold ×684%
Silver ×414%
Bronze ×22%
Usable CPU
114 threads
Max reservation
150 GHz
Usable memory
704 GB
ESXi host capacitythe provider

The physical host. Usable capacity removes hypervisor overhead; reservation is capped at base clock.

Usable after overhead
Threads (HT)128 threads
Usable CPU (utilisation)114 threads
Max CPU reservation150 GHz
Usable memory704 GB
VM sizingthe consumer

One representative VM per class. Gold is 4× Bronze, Silver 2×. Utilisation and reservation are set per class.

CPU utilisation (together)50 %
Memory utilisation (together)85 %
Gold CPU reserved50 %
Gold memory reserved100 %

Silver and Bronze halve each step: CPU 50 / 25 / 12.5%, memory 100 / 50 / 25%

One VM per class
Gold VM16 vCPU · 64 GB
Silver VM8 vCPU · 32 GB
Bronze VM4 vCPU · 16 GB
Classes of serviceGold · Silver · Bronze

Overcommit ratios per class. CPU and memory each have their own; Bronze is the densest. Set how many of each class run on this host.

GoldSilverBronze
Number of VMsthe mix
CPU overcommitvCPU : thread
Memory overcommitvs DRAM
Allocation capacityvCPU · GB114 vCPU704 GB228 vCPU845 GB342 vCPU986 GB
Reserved per VMGHz · GB20 GHz64 GB5 GHz16 GB1.25 GHz4 GB
Expected use per VMvCPU · GB8 vCPU54.4 GB4 vCPU27.2 GB2 vCPU13.6 GB
VMs in this mix
12 VMs
136 vCPU · 544 GB vRAM
Fits before 100%
11.9 VMs
this mix, scaled to full capacity
Binding constraint
101%
Allocation CPU is the limit
Planned consumptionaim for 90 to 110%
Allocationbinding · CPU
Configured size divided by each class’s overcommit, against usable threads and memory.
CPU
101%
Memory
73%
Reservation
What each class reserves, against the max CPU reservation and usable memory.
CPU
95%
Memory
65%
Utilisation
Expected use of the configured size, plus hypervisor overhead, against usable capacity.
CPU
72%
Memory
75%
Allocation CPU is the limit at 101%: on target.
The binding model sits inside 90 to 110%, the band the worksheet aims for.

You run out of capacity when any number reaches 100%. Green is 90 to 110%; amber is headroom; red is over capacity.

Cost comparisonfive years, per host

Public cloud has no class of service: every VM is priced the same. Private cloud cost is per host over five years.

5-yr savings vs public
$68,000
private cloud vs public, per host
Public cloud over 5 years$233,240
Private cloud over 5 years / host$165,000
Public cloud annual (this mix)$46,648
Capacity reserved for HA (1 of hosts)10%
In the guidethe book on capacity

The book’s mixed-workload example puts utilisation, reservation, allocation and contention together across three classes of service, with a consistent 2x gap between Gold, Silver and Bronze. This planner is the spreadsheet that comes with it.

The worksheetXLSX · 296 KB · 25 Jul 2026

Interactive version of the Capacity Planning worksheet from the guide. Defaults reproduce it; change any input to model your estate. As the book says, confirm the size of your ESXi host first.

Download the worksheet