Infrastructure Utilization Calculator
Score CPU, memory, storage and network utilisation together to find stranded capacity and the annual cost of the waste.
Inputs
The utilisation you aim for, leaving failover and spike headroom.
Editable placeholder — hardware, licensing, power and support for this estate.
Overall Utilisation
56.0%
Stranded Capacity
19.0%
Annual Cost of Stranded Capacity
$91,200.00
Resource Balance Score
28/ 100
Most Under-used Resource
Network at 18% against Memory at 78%
Utilisation Grade
D — Weak
Step by step
Values used
CPU utilisation = 42 %; Memory utilisation = 78 %; Storage utilisation = 61 %; Network utilisation = 18 %; Target utilisation = 75 %; Annual infrastructure cost = 480,000 USD
Infrastructure Utilization
overall = CPU × 0.35 + memory × 0.35 + storage × 0.20 + network × 0.10; stranded = target − overall; waste = annual cost × stranded ÷ 100.
Overall Utilisation
= 56.0
Stranded Capacity
= 19.0
Annual Cost of Stranded Capacity
= 91,200.00
Resource Balance Score
= 28 / 100
Most Under-used Resource
= Network at 18% against Memory at 78%
Utilisation Grade
= D — Weak
How it works
Utilisation is only meaningful alongside balance. An estate at 42% CPU and 78% memory is not half empty — it is memory bound with stranded CPU that cannot be sold, because the next VM needs both. The spread between the highest and lowest resource is therefore a better refresh signal than any single average. Stranded capacity is fully paid for and unusable, so the balance score points directly at what the next hardware refresh should change — more memory per socket rather than more sockets, for instance. Replace the cost figure with your own fully loaded annual spend.
Formula
Infrastructure Utilization
overall = CPU × 0.35 + memory × 0.35 + storage × 0.20 + network × 0.10; stranded = target − overall; waste = annual cost × stranded ÷ 100.
- overall utilisation
- Weighted blend, with CPU and memory carrying most of the weight
- stranded capacity
- Gap between target and actual utilisation that you are still paying for
- balance score
- 100 minus the spread between the highest and lowest resource
Frequently Asked Questions
How is Infrastructure Utilization calculated?
overall = CPU × 0.35 + memory × 0.35 + storage × 0.20 + network × 0.10; stranded = target − overall; waste = annual cost × stranded ÷ 100. Utilisation is only meaningful alongside balance. An estate at 42% CPU and 78% memory is not half empty — it is memory bound with stranded CPU that cannot be sold, because the next VM needs both. The spread between the highest and lowest resource is therefore a better refresh signal than any single average.
Why does Infrastructure Utilization matter?
Stranded capacity is fully paid for and unusable, so the balance score points directly at what the next hardware refresh should change — more memory per socket rather than more sockets, for instance. Replace the cost figure with your own fully loaded annual spend.
What values do I need to enter?
This calculator takes 6 inputs: CPU utilisation, Memory utilisation, Storage utilisation, Network utilisation, Target utilisation, Annual infrastructure cost. 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 is 100% utilisation not the target?
Failover capacity, scheduling headroom and burst absorption all live in the unused fraction. A target of 70-80% is the practical optimum: below it you are wasting money, above it a single host failure or workload spike has nowhere to go.
You might also need
- Hypervisor Consolidation CalculatorCommonly used together
- Cluster Expansion CalculatorCommonly used together
- Virtualization Ratio CalculatorCommonly used together
- OpenShift Cluster Health CalculatorCommonly used together
- OpenShift Node Capacity CalculatorAlso in Virtualization & Private Cloud
- VMware VM Density CalculatorAlso in Virtualization & Private Cloud