Skip to content
Calcrivo

Server Consolidation Calculator

Calculate how many target servers are needed to consolidate workloads, with a safety margin.

Inputs

e.g. 1.3 reserves 30% headroom for peak load and failover

New Servers Needed

4

Consolidation Ratio (workloads : server)

5.0

Total Raw Resource Demand

80.0

Adjusted Demand (with safety margin)

104.0

Avg Workloads per Server

5.0

Step by step

  1. Values used

    Number of Workloads to Consolidate = 20; Avg Resource Demand per Workload (vCPU-equivalent units) = 4; Target Server Capacity (same units) = 32; Safety Margin Factor = 1.30

  2. Servers needed

    new_servers = ceil( sum(workload_resources) × safety_factor / target_server_capacity )

  3. New Servers Needed

    = 4

  4. Consolidation Ratio (workloads : server)

    = 5.0

  5. Total Raw Resource Demand

    = 80.0

  6. Adjusted Demand (with safety margin)

    = 104.0

  7. Avg Workloads per Server

    = 5.0

How it works

Server consolidation (physical-to-virtual, or virtual-to-larger-virtual) sums the resource demand of every workload being combined, applies a safety margin to account for peak/bursty load and N+1 failover headroom (since workloads rarely all peak simultaneously but occasionally several will), and divides by each target server's usable capacity, rounding up since a fraction of a server isn't a deployable unit. Skipping the safety factor and sizing to exactly average demand risks resource contention the moment several consolidated workloads spike concurrently.

Formula

Servers needed

new_servers = ceil( sum(workload_resources) × safety_factor / target_server_capacity )

R_i
resource demand of workload i
f
safety factor
C
target server capacity

Frequently Asked Questions

Why not just size for total average demand without a safety factor?

Average demand assumes perfectly smooth, non-overlapping load, but real workloads have correlated peaks (e.g. multiple batch jobs scheduled at similar times, traffic spikes hitting several services together) — a safety factor (commonly 1.2-1.5x) reserves headroom so simultaneous peaks don't cause resource contention, throttling, or OOM conditions across the consolidated host.

How should overcommit ratios factor into virtualization consolidation?

Hypervisors can overcommit vCPU (scheduling more virtual cores than physical cores exist, since not every VM uses its allocation simultaneously) at ratios commonly cited around 2:1 to 4:1 for general workloads, but memory overcommit is riskier and workload-dependent — this calculator's safety factor should be tuned down if the target platform's overcommit already accounts for some of that peak-smoothing.

Does consolidation ratio alone tell you if consolidation is a good idea?

No — a high consolidation ratio (many workloads per server) reduces hardware and licensing costs but increases the blast radius of a single host failure and can create noisy-neighbor performance issues; consolidation decisions should weigh the ratio against availability requirements and isolation needs, not optimize for ratio alone.

You might also need

Related Calculators

Boot Time CalculatorKernel Parameter CalculatorPackage Dependency Calculator