Grace Blackwell needs a new scheduler: 27% more usable GPUs from the same racks
wondersky
135 points
21 comments
October 29, 2026
Related Discussions
Found 5 related stories in 138.1ms across 10,991 title embeddings via pgvector HNSW
- Hetzner: The New GPU Server GEX63 for Professional AI Workloads tosh · 14 pts · October 12, 2026 · 56% similar
- Benchmarking 15 “E-Waste” GPUs with Modern Workloads eso_logic · 123 pts · July 13, 2026 · 55% similar
- "Two 2030 AMD racks are expected to deliver same compute as 570 racks in 2024" lossolo · 11 pts · August 19, 2026 · 54% similar
- Self-hosting Kimi K3: 20% more hardware cost, 20% better task resolution flifenstein · 130 pts · July 29, 2026 · 53% similar
- Show HN: PantheonGPU – GPU health testing and AI workload benchmarking saqibkhan1992 · 13 pts · August 18, 2026 · 49% similar
Discussion Highlights (5 comments)
jhgg
This blog post spends a lot of time telling why gang scheduling is needed here (a fact obvious to anyone using the nvl72s), but doesn't actually go into detail about how their scheduler works. At work, we have built something very similar, a custom topology aware scheduler for workloads, and the most interesting things about such a project are entirely absent from this article, making it more of a fluff/marketing piece than an actually interesting technical blog in this area. Our next iteration of this scheduler aims to scale to O(millions) of GPUs, with a scheduling cycle time measured in the milliseconds.
novalite
This reads a bit disingenuous and click-baity. There's no "new" scheduler. Gang scheduling and rack-aware scheduling have been around since the days of HTCondor, and are put in practice at almost every large GPU deployment I've seen. The net new information added by this blog is close to zero, and feels like shilling for SkyPilot.
zan2215
"Not all high-speed interconnects are created equal" I think he's a red rising fan
timzaman
Who has nvl72s that this isnt absolutely plainly obvious to - and has been for years. Not just that - topology has -always- been relevant to scheduling, and hpc schedulers have always been aware. What a weird blogpost.
asaiacai
There’s been some prior art in this space I feel that should be mentioned from k8s SIG batch in the Kueue project https://kueue.sigs.k8s.io/docs/concepts/topology_aware_sched...