06A multi-node training job sits Pending forever while the cluster shows free GPUs. What is happening?▼hardNVIDIAMetaDatabricks2 notes & commentsunlockedThe default scheduler places pods one at a time, which is exactly wrong for a job that needs all sixteen or none. Two half-placed jobs can hold each other's GPUs forever without either ever starting.Open full answer →
10Training throughput is 40 percent below what the GPU count predicts. The GPUs look fine. Where do you look?▼expertNVIDIAMetaMicrosoft2 notes & commentsunlockedAt sixteen GPUs and above, the network is the computer. Collectives run at the speed of the worst link in the group, and placement decides which link that is.Open full answer →
35How often should a large training run checkpoint, and what does the answer depend on?▼hardNVIDIAMetaMicrosoft2 notes & comments◆ premiumCheckpoint too rarely and a failure costs hours of GPU time. Checkpoint too often and you pay for stalled GPUs writing terabytes to storage. There is an arithmetic answer and most teams never do it.Open full answer →
37At 512 GPUs something fails every few hours. How does a training run survive that?▼expertNVIDIAMetaMicrosoft2 notes & comments◆ premiumFailure stops being an event and becomes a rate. Once mean time between failures drops below the length of a run, the design question is not how to avoid interruption but how cheaply you can absorb one.Open full answer →