Why NVL72 scale-up bandwidth sits mostly idle — cutting it won't hurt inference
bookwormengr · x · 2026-10-26
A technical argument on why reducing scale-up bandwidth in large domains like NVL72 likely won't degrade performance:
- In DP-EP deployments, scale-up bandwidth only moves activations between DP and EP — tiny traffic relative to available bandwidth, even at large batch sizes.
- Only Tensor Parallel stresses GPU-GPU links heavily, but with large scale-up domains operators prefer DP-EP over DP-TP anyway.
- Most in-domain bandwidth consumption is GPU-HBM traffic (weights and KV cache reads), a different pool from NVLink; HBM saturates while GPU-GPU links stay mostly idle.
- Training uses scale-up bandwidth more heavily but still doesn't saturate it.
More from Infra
- RTX 4090 workstation vs AI subscriptions: an editor's break-even math — iamthecarguy1234 · 2026-10-26
- Cerebras CS-4 teardown: 2x bandwidth and power, 50% fewer parts vs CS-3 — jwt0625 · 2026-10-26
- theo doubts Windows ARM: porting 20 years of tech debt vs Intel improving — wateriscoding · 2026-10-26
- TokenSpeed's Three-Language Stack: C++ for Correctness, Rust for Agents, Python for Glue — zhyncs42 · 2026-10-26
- Speculative Decoding Explained: a 30% Wrong Guesser Never Changes the Output — anbarth · 2026-10-26
- You Can Train a 1B Model in 3 Weeks: Dev Shares 15.9-Day Training Run Log — arthurcolle · 2026-10-26