Servers, Storage and Virtualization · #48

Online VM CPU and RAM Capacity Planner

Compares the total vCPU and RAM of virtual machines with host capacity.

  • Data is processed in your browser and not sent to a server

Tool

Total across sockets, excluding HT.

General servers 3–4, VDI 6–8, SQL 1–2.

For hypervisor and management (e.g. 8–16 GiB).

Per line: name;vCPU;RAM GiB;count

What does this tool do?

In virtualization CPU can be overcommitted, RAM practically cannot: when RAM overflows the host pages and every VM slows down. The tool treats RAM as a hard limit and vCPU as a soft limit at your chosen ratio, after subtracting the host and hypervisor reserve.

How to use it

  1. Enter physical host cores (excluding hyper-threading) and the target vCPU:core ratio.
  2. Enter host RAM and the reserve for the hypervisor/parent partition.
  3. Enter VMs one per line as name;vCPU;RAM GiB;count (count optional) and press Calculate.

Fields

Physical cores
Total across sockets, excluding HT.
vCPU:core ratio
General servers 3–4, VDI 6–8, SQL 1–2.
Host RAM
Host reserve
For hypervisor and management (e.g. 8–16 GiB).
VM list
Per line: name;vCPU;RAM GiB;count

Worked example

InputValue
Physical cores32
vCPU:core ratio4
Host RAM256
Host reserve16
VM list
SQL01;8;64
APP;4;16;6
DC01;2;8;2
FILE01;4;24

Expected result: 200 GiB of 240 GiB usable RAM is used, 40 GiB free; 40 vCPU is below the 128 vCPU capacity (ratio 1.25:1).

RAM and CPU fit. 40 GiB of free RAM may not absorb VMs from another host during maintenance; use the N+1 tool for clusters.

Second scenario

InputValue
Physical cores24
vCPU:core ratio3
Host RAM192
Host reserve12
VM list
RDS;8;32;4
SQL01;12;64
DC01;2;8

Expected result: RAM is exceeded by 20 GiB (200 GiB of VMs, 180 GiB usable); vCPU fits. This host is too small for the list.

Method and assumptions

Usable RAM = host RAM − reserve. vCPU capacity = cores × ratio. Row total = value × count. Dynamic memory, ballooning and page sharing are ignored.

Using the result and troubleshooting

If RAM is negative, spread VMs to another host or add RAM. If the ratio is exceeded, verify the real impact with CPU Ready (VMware) or CPU wait time (Hyper-V).

Limits and common mistakes

  • NUMA boundaries, licensing and resources such as GPUs are not evaluated.

Frequently asked questions

Should hyper-threads count as cores?

Use physical cores for the ratio; HT adds roughly 15–30 % capacity but does not double cores.

Related tools and service

Related service: Virtualization and Data Management

Systems online tools · See all online tools