AI Racks Explained

AI Racks Explained

The machines underneath, chip to data centre.

An interactive guide to the machines underneath AI: packages, NVLink racks, networks, power and cooling, with every hardware figure sourced and dated.

  1. Package1 GPU
    HBM 8 TB/s
  2. Compute tray4 GPUs
    NVLink 900 GB/s
  3. Rack72 GPUs
    NVLink 900 GB/s
  4. Scalable unit576 GPUs
    InfiniBand 50 GB/s
  5. SuperPOD9,216 GPUs
    InfiniBand 50 GB/s
  6. Hall59,976 GPUs
    InfiniBand 50 GB/s
Bandwidth one GPU has at each rung of a GB200 NVL72 cluster, log scale. HBM is a read rate; the rest are per direction.

How this is checkedEvery hardware figure carries its source and the date it was read. The model is cross-checked against published rack, switch and fabric totals it does not take as inputs, and its collectives against a measured NCCL all-reduce. How it is tested →

What you'll learn

A large model is trained and served by thousands of GPUs, and the way they are packaged, wired, powered and cooled decides what is fast. Inside one package a GPU reads its HBM at 8 TB/s. Inside an NVLink rack it reaches any of 72 GPUs at 900 GB/s per direction. One rung further out, over the network, it has 50 GB/s: a drop of 18 times. Most of the design of a training or inference cluster is about which traffic crosses which boundary.

Each chapter is built around an animation whose every frame comes from a small model tested against a Python reference. Every hardware figure carries its source and the date it was read, products whose specifications are preliminary or planned are marked, and the model is checked against published figures (its checks, labelled by what each one tests).

The centrepiece

Chapter 8 serves 1,500 requests on one 72-GPU rack with prefill and decode in separate pools, running a tested discrete-event simulator in your browser: split the rack, change the link the KV cache crosses, or put a cheaper context-optimised part in one pool, and watch latency and energy per token move.

Every hardware figure the model uses, with its source and access date: the specifications.

Built by a hardware engineer

The author designs hardware: the RTL, SoC and signal-integrity work behind this track is public too.

Part of the companion sites' Hardware track, with GPU Kernels Explained (how one GPU executes the maths) and Systolic Arrays Explained (inside a matrix engine). What runs on these machines: Training and Serving. How this site was built, and how to check it: about.