Eight GPUs per NVLink domain shaped every serving layout of the Hopper era. Seventy-two moves the boundary that expert parallelism and KV transfer used to cross over the NIC. The answer prices what moves inside the rack, what still does not fit, and the failure mode that comes with it.
← Distributed & Disaggregated Inference / 10
expertNewNVIDIAMicrosoft (Microsoft AI)OpenAI
A GB200 NVL72 puts 72 GPUs in one NVLink domain. What does that change for MoE serving and for prefill-decode disaggregation?
Eight GPUs per NVLink domain shaped every serving layout of the Hopper era. Seventy-two moves the boundary that expert parallelism and KV transfer used to cross over the NIC. The answer prices what moves inside the rack, what still does not fit, and the failure mode that comes with it.
Updated Oct 2026 · Worked answers on inference mechanisms, with calculations, implementation details, and follow-up questions.
an account raises the free count per topic
UP NEXT ON YOUR JOURNEY
Next in this trackA 128k-token prefill takes 10 seconds on one node. How does context parallelism split it across nodes, and what does it send?Next in this trackA multi-node MoE deployment's TPOT doubled overnight, and one network link is degraded. How do you find it, and how do you design around it?Next in this trackEach decode layer needs the previous all-to-all to finish. How do you overlap communication with compute anyway, and at what cost?
DISCUSSION · 0
Nobody has commented on this answer. Add a correction or another way to work it.