keepcalculator

06 Numbers and Powers

Estimate Data Center Power for AI Workloads

Card No. 06·16378 · Updated · Standard formula, shown below

This guide walks you through estimating the power requirements for AI workloads in a data center, from initial planning to final numbers. You’ll learn how to account for compute hardware, cooling, and facility overhead, and get a realistic estimate of total power draw. You’ll need basic specs of your planned hardware and a clear idea of your workload’s intensity.

What You’ll Need

  • Server specifications: GPU or accelerator model, CPU model, number of servers.
  • Power supply unit (PSU) ratings for each server type.
  • Cooling system type (air, liquid, or hybrid) and its efficiency.
  • Facility details: UPS efficiency, PDU losses, lighting and miscellaneous loads.
  • Workload profile: expected GPU utilization (e.g., training vs. inference).
  • A spreadsheet or calculator to organize the data.

Step-by-Step

  1. List your compute nodes. Write down each server model and the number of units. For each, note the maximum power draw of the GPU(s) and CPU. For example, an NVIDIA H100 has a max TDP of 700W, and a typical dual-socket CPU server might draw 400W for the CPUs.
  2. Calculate per-server peak power. Add the GPU power (multiplied by number of GPUs per server), CPU power, and a baseline for memory, storage, and motherboard (typically 50-100W). For a server with 8 H100s: 8 x 700W = 5600W for GPUs, plus 400W CPU, plus 100W baseline = 6100W per server.
  3. Apply utilization factor. AI training often runs GPUs near 100% utilization, but inference may be lower. Multiply per-server peak by expected utilization (e.g., 0.9 for training, 0.5 for inference). For training at 90%: 6100W x 0.9 = 5490W per server.
  4. Multiply by number of servers. If you have 100 servers, total IT load = 5490W x 100 = 549,000W = 549kW.
  5. Add network and storage. Include top-of-rack switches (typically 100-300W each) and storage arrays. For a large cluster, add 5-10% of IT load for network and storage. Here, 10% of 549kW = 54.9kW, so IT total = 603.9kW.
  6. Account for cooling. Determine the cooling system’s power overhead. For air cooling, a common rule of thumb is that cooling consumes about 30-50% of IT load. For liquid cooling, it’s lower, around 10-20%. Use 40% for air: 603.9kW x 0.4 = 241.6kW for cooling.
  7. Include facility overhead. Add power for UPS losses (typically 5-10% of IT load), PDU losses (1-2%), and lighting/other (1-2%). Combine these as a factor of IT load: 10% UPS + 2% PDU + 2% misc = 14%. 603.9kW x 0.14 = 84.5kW.
  8. Sum all components. Total power = IT load + cooling + facility overhead = 603.9kW + 241.6kW + 84.5kW = 930kW.
  9. Add a safety margin. For future growth or unexpected spikes, add 20-30%. 930kW x 1.25 = 1162.5kW. This is your estimated total power requirement.

Common Mistakes

  • Using peak power instead of actual utilization. GPUs rarely run at 100% continuously; using max TDP overestimates significantly.
  • Forgetting cooling overhead. Cooling can be as much as half the IT load; omitting it leads to a severely underpowered facility.
  • Ignoring PSU efficiency. The power drawn from the wall is higher than the server’s component draw due to PSU losses. Use an efficiency factor (e.g., 94% for Platinum PSUs) to get true input power.
  • Not accounting for redundancy. If you need N+1 redundancy for cooling or UPS, that adds extra capacity.
  • Mixing units. Be consistent with kW vs. MW; a decimal error can be catastrophic.

Tips

  • Measure actual power from a pilot cluster if possible; it’s more accurate than theoretical calculations.
  • Use power monitoring tools on existing infrastructure to get real utilization data.
  • Consider future upgrades—newer GPUs may have higher power draw, so leave headroom.
  • For liquid cooling, remember to include pump and CDU (coolant distribution unit) power, not just the chillers.
  • Check local climate—cooler regions may allow free air cooling, reducing power.

Troubleshooting

  • Estimate seems too high. Re-check utilization factors. Maybe you’re using peak TDP for GPUs that actually throttle. Also verify if the cooling factor is appropriate—some modern designs use direct-to-chip liquid cooling with much lower overhead.
  • Estimate seems too low. Ensure you included all auxiliary equipment: network switches, storage, management servers, and monitoring. Also, check if you accounted for power distribution losses inside the server (voltage regulators).
  • Conflicting vendor specs. If GPU datasheets list both ‘typical’ and ‘maximum’ power, use typical for sustained workloads and maximum for sizing circuit breakers.
  • Uncertain about utilization. For a conservative estimate, use 100% utilization for training clusters, but for inference, use a realistic average based on expected traffic.

Frequently Asked Questions

  1. How much power does a single AI server typically draw? A high-end server with 8 GPUs can draw 5-10 kW under load, depending on GPU model and utilization.
  2. What is PUE and how does it relate? Power Usage Effectiveness is the ratio of total facility power to IT equipment power. A PUE of 1.5 means for every 1kW of IT load, 0.5kW is used for cooling and overhead.
  3. Can I use a simple multiplier for cooling? Yes, a common rule is 1.3-1.5 times IT load for air-cooled facilities, but liquid cooling can bring that down to 1.1-1.2.
  4. How do I account for GPU throttling? If your cooling is insufficient, GPUs may throttle, reducing power draw but also performance. Use thermal design power (TDP) as a maximum, but actual draw may be lower.
  5. What about power for networking? Include switches, routers, and cabling. For a large cluster, this can add 5-10% to IT load.
  6. Is it better to overestimate? Yes, it’s safer to overestimate for capacity planning, but be aware that overestimating leads to higher initial costs for power infrastructure.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →