Hypervisor Consolidation Calculator
Work out how many hypervisor hosts replace a fleet of physical servers, and the capex and power that consolidation changes.
Inputs
Standalone servers typically run at 5-15% CPU.
Editable list price — use your own quote, hardware pricing moves constantly.
Hypervisor Hosts Required
3hosts
Consolidation Ratio
20.0:1
Hardware Capital Cost
$54,000.00
Annual Electricity Saving
$22,811.04
Power Draw Reduction
88.6%
Sizing Driver
Memory drives the host count — buy larger DIMM configurations, not more sockets
Step by step
Values used
Physical servers to consolidate = 60 servers; Cores per physical server = 8 cores; Average CPU utilisation today = 12 %; Memory per physical server = 32 GiB; Average memory utilisation today = 45 %; Cores per new hypervisor host = 32 cores; Memory per new hypervisor host = 512 GiB; Target utilisation on new hosts = 70 %; vCPU per physical core = 4 ratio; Purchase price per hypervisor host = 18,000 USD; Power draw per physical server = 350 W; Power draw per hypervisor host = 800 W; Electricity price = 0.1400 USD/kWh
Hypervisor Consolidation
hosts = max(consumed cores ÷ (host cores × overcommit × target utilisation), consumed memory ÷ (host RAM × target utilisation × 0.94)), rounded up.
Hypervisor Hosts Required
= 3 hosts
Consolidation Ratio
= 20.0 :1
Hardware Capital Cost
= 54,000.00
Annual Electricity Saving
= 22,811.04
Power Draw Reduction
= 88.6
Sizing Driver
= Memory drives the host count — buy larger DIMM configurations, not more sockets
How it works
Consolidation works because standalone servers sit almost idle: sizing against measured consumption rather than installed capacity is what produces ratios of 15:1 or better. CPU can then be overcommitted, but memory cannot, so the memory side usually decides the host count while the CPU side decides whether the overcommit ratio is defensible. Consolidation business cases live or die on the ratio, and sizing from installed cores instead of consumed cores understates the ratio by an order of magnitude — while ignoring the memory constraint overstates it. Treat the capex and electricity figures as editable placeholders and substitute your own quotes and tariff.
Formula
Hypervisor Consolidation
hosts = max(consumed cores ÷ (host cores × overcommit × target utilisation), consumed memory ÷ (host RAM × target utilisation × 0.94)), rounded up.
- consumed cores
- Physical cores × measured utilisation, not installed cores
- target utilisation
- Utilisation you want the new hosts to run at, leaving headroom
- 0.94
- Roughly 6% of host memory lost to hypervisor overhead
Frequently Asked Questions
How is Hypervisor Consolidation calculated?
hosts = max(consumed cores ÷ (host cores × overcommit × target utilisation), consumed memory ÷ (host RAM × target utilisation × 0.94)), rounded up. Consolidation works because standalone servers sit almost idle: sizing against measured consumption rather than installed capacity is what produces ratios of 15:1 or better. CPU can then be overcommitted, but memory cannot, so the memory side usually decides the host count while the CPU side decides whether the overcommit ratio is defensible.
Why does Hypervisor Consolidation matter?
Consolidation business cases live or die on the ratio, and sizing from installed cores instead of consumed cores understates the ratio by an order of magnitude — while ignoring the memory constraint overstates it. Treat the capex and electricity figures as editable placeholders and substitute your own quotes and tariff.
What values do I need to enter?
This calculator takes 13 inputs: Physical servers to consolidate, Cores per physical server, Average CPU utilisation today, Memory per physical server, Average memory utilisation today, Cores per new hypervisor host, Memory per new hypervisor host, Target utilisation on new hosts, vCPU per physical core, Purchase price per hypervisor host, Power draw per physical server, Power draw per hypervisor host, Electricity price. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Why size against consumed rather than installed capacity?
A physical server bought for peak load runs at roughly 10% average CPU, so its installed cores are mostly idle capacity you are paying to cool. Virtualisation's whole value is reclaiming that gap, which only appears if you size on measured consumption plus headroom.
You might also need
- VMware VM Density CalculatorCommonly used together
- Virtualization Ratio CalculatorCommonly used together
- OpenStack Nova Capacity CalculatorCommonly used together
- Infrastructure Utilization CalculatorCommonly used together
- OpenShift Node Capacity CalculatorAlso in Virtualization & Private Cloud
- Cluster Expansion CalculatorAlso in Virtualization & Private Cloud