RTFM HPC - Why Jobs Wait

Hey! I'd love to hear your thoughts, send me a voice note. #SLURM101: Why Jobs Wait (and Why They Sometimes Don't) You submit a job. Then someone else submits a job after you, and it starts first. Is Slurm broken? Is somebody cheating the queue? No. This is Slurm working exactly as designed. In this episode we follow one job, job 42, through its life in Slurm and look at the quiet decisions the scheduler makes along the way. No command syntax, no config files: just the concepts, so the commands and options stop looking like magic spells. What you will learn: - Backfill scheduling: why a small job can start before a big one - Partitions: separate pools of nodes with their own rules - Features (constraints): labels on nodes, like the GPU model or local storage - Topology-aware scheduling: keeping a job's nodes close together on the network - TRES (trackable resources): GPUs, memory, licenses and other countable things - QoS (quality of service): fair sharing when one group floods the queue - Plugins: adding your own logic, for example Pyxis for containers More info about HPC in the book https://a.co/d/b03YNBn