Servers, Storage and Virtualization · #50
Online Server Consolidation Planner
Turns a physical server inventory into virtual requirements (vCPU, RAM, disk, host count).
- Data is processed in your browser and not sent to a server
- Export: CSV
Tool
What does this tool do?
When virtualizing physical servers, adding up nameplate values (cores, installed RAM) overstates host needs two- to threefold, while average usage alone causes bottlenecks at peak times. The tool derives requirements from peak CPU and used RAM, adds 25 % CPU and 10 % RAM headroom, sizes servers without measurements with conservative assumptions (CPU 100 %, RAM = installed) and flags them clearly.
How to use it
- CSV header:
server, cores, cpu_peak, ram_gb, ram_used_gb, disk_gb, group(server, cores and ram_gb required). - Enter growth and the target host's cores, RAM, reserve and vCPU ratio.
- Press Calculate; download the table as CSV.
Fields
- Server inventory (CSV)
- cpu_peak = busiest period percentage; if ram_used_gb is empty installed RAM is used.
- Growth
- Expected increase over the planning period.
- Host cores
- Physical cores per target host.
- vCPU:core ratio
- Host RAM
- Host reserve
Worked example
| Input | Value |
|---|---|
| Server inventory (CSV) | |
| Growth | 20 |
| Host cores | 32 |
| vCPU:core ratio | 4 |
| Host RAM | 384 |
| Host reserve | 16 |
Expected result: 6 servers fit on one host (2 with N+1): 49 vCPU and 352 GiB RAM against 128 vCPU / 368 GiB per host; FILE01 has no RAM measurement, so installed 16 GB was used.
RAM determines the host count and a single host is 96 % full; once the growth headroom is used a second host becomes mandatory. With a FILE01 measurement the requirement may drop. The ad and erp groups are listed as dependencies: move servers of the same group together and place DCs on different hosts.
Second scenario
| Input | Value |
|---|---|
| Server inventory (CSV) | |
| Growth | 0 |
| Host cores | 16 |
| vCPU:core ratio | 3 |
| Host RAM | 256 |
| Host reserve | 12 |
Expected result: WEB01 and WEB02 have no peak CPU measurement; 100 % was assumed and both rows are marked amber.
Method and assumptions
Required vCPU = ceil(cores × peak % × (1 + growth) × 1.25), at least 1. Required RAM = ceil(used RAM × (1 + growth) × 1.10).
Hosts = max(ceil(total vCPU / (host cores × ratio)), ceil(total RAM / (host RAM − reserve))). One host is added for N+1.
Using the result and troubleshooting
Collect at least two weeks of performance data for servers without measurements (perfmon, sar or your monitoring system). Validate the result with the VM vCPU/RAM and N+1 tools.
Limits and common mistakes
- Disk IOPS, network traffic and licensing constraints are not considered; disk is shown as a total only. Performance differences between CPU generations are not normalized.
Frequently asked questions
Can I use average CPU instead of peak?
Not recommended. Averages drop with night hours; size by the 95th percentile or business-hours peak.
Related tools and service
- VM CPU and RAM Capacity PlannerCompares the total vCPU and RAM of virtual machines with host capacity.
- Hyper-V Cluster N+1 Capacity PlannerTests for each host failure whether the VMs can be placed on the remaining hosts by RAM.
- Server Power and Cooling CalculatorCalculates energy, heat load and cost from device power consumption.
Related service: Virtualization and Data Management