Episode Details

Back to Episodes
How Slurm and Kubernetes Split GPU Workloads

How Slurm and Kubernetes Split GPU Workloads

Episode 6552 Published 1 day, 22 hours ago
Description
Standing up a GPU cluster splits into two stacked problems: scheduling jobs onto hardware and keeping collective communication fast. Distributed training stalls if even one GPU is missing, yet Kubernetes's default scheduler places pods one at a time. This walkthrough compares Slurm's atomic batch queues with Kubernetes tools like the NVIDIA GPU Operator, Kueue, Volcano, KubeRay, and Kubernetes 1.37's gang scheduling—explaining why national labs and 66% of organizations running generative models split training and inference across both systems. Key sources: • NVIDIA, , retrieved 2026-11-13; latest release v26.7.2 (2026-10-14). — https://github.com/NVIDIA/gpu-operator • NVIDIA, , retrieved 2026-11-13; latest release v2.32.6-1 (2026-11-09). — https://github.com/NVIDIA/nccl • AMD, , retrieved 2026-11-13; repo marked retired, moved to ROCm/rocm-systems; latest release rocm-7.2.4 (2026-05-28). — https://github.com/ROCm/rccl Episode 6552 — myweirdprompts.com/n/6552 (permanent short link: myweirdprompts.com/740787) Listen on Android: MWP FM Player — myweirdprompts.com/apk
Listen Now

Love PodBriefly?

If you like Podbriefly.com, please consider donating to support the ongoing development.

Support Us