Work out bare metal sizing instantly with clear inputs, formula shown and shareable results.
Bare-metal sizing takes the larger of the CPU and memory requirements, each derated for target utilisation — 75 percent on cores and 85 percent on memory is typical — then adds one server for N+1 redundancy so a single failure does not reduce capacity below peak demand. Which resource drives the count tells you what to specify differently next refresh.
Server count
CPU count = ceil(vCPU demand / (cores x 0.75)); memory count = ceil(memory demand / (RAM x 0.85)); servers = max + 1 for N+1
Because CPU demand is spikier. Memory is allocated and held, so it can be planned closer to the limit provided there is no overcommit.
For a single rack or fault domain, usually. Across availability zones you need enough spare that losing a whole zone still leaves capacity, which is N+1 per zone.