Slurm Workload Manager
Free and open-source job scheduler for Linux and similar computers
From Wikipedia, the free encyclopedia
The Slurm Workload Manager, formerly known as Simple Linux Utility for Resource Management (SLURM), or simply Slurm, is a free and open-source job scheduler for Linux and Unix-like kernels, used by many of the world's supercomputers and computer clusters.
| Slurm | |
|---|---|
| |
| Developer | SchedMD |
| Stable release | |
| Written in | C |
| Operating system | Linux |
| Type | Job Scheduler for Clusters and Supercomputers |
| License | GNU General Public License, version 2.0[3] |
| Website | slurm |
| Repository | |
Slurm uses a best-fit algorithm based on Hilbert curve scheduling or fat tree network topology in order to optimize locality of task assignments on parallel computers.[4] It provides three key functions:
- allocating exclusive and/or non-exclusive access to resources (computer nodes) to users for some duration of time so they can perform work,
- providing a framework for starting, executing, and monitoring work, typically a parallel job such as Message Passing Interface (MPI) on a set of allocated nodes, and
- arbitrating contention for resources by managing a queue of pending jobs.
History
Slurm began development as a collaborative effort primarily by Lawrence Livermore National Laboratory, SchedMD,[5] Linux NetworX, Hewlett-Packard, and Groupe Bull as a Free Software resource manager. The first release happened in 2002.[6] It was inspired by the closed source Quadrics RMS and shares a similar syntax. The name is a reference to the soda in Futurama.[7] Over 250 people around the world have contributed to the project. It has since evolved into a sophisticated batch scheduler capable of satisfying the requirements of many large computer centers.
In 2010, the developers of Slurm founded SchedMD, which maintains the canonical source, provides development, level 3 commercial support and training services. Commercial support is also available from Bull, Cray, and Science + Computing (subsidiary of Atos).[citation needed]
As of November 2021[update], Slurm is the workload manager on about 60% of the TOP500 supercomputers.[8]
Structure
Slurm's design is very modular with about 100 optional plugins. In its simplest configuration, it can be installed and configured in a couple of minutes. More sophisticated configurations provide database integration for accounting, management of resource limits and workload prioritization.
Supported platforms
Recent Slurm releases run only on Linux. Older versions had been ported to a few other POSIX-based operating systems, including BSDs (FreeBSD, NetBSD and OpenBSD),[9] but this is no longer feasible as Slurm now requires cgroups for core operations. Clusters running operating systems other than Linux will need to use a different batch system, such as LPJS.[10] Slurm also supports several unique computer architectures, including:
- IBM BlueGene/Q models, including the 20 petaflop IBM Sequoia
- Cray XT, XE and Cascade
- Tianhe-2 a 33.9 petaflop system with 32,000 Intel Ivy Bridge chips and 48,000 Intel Xeon Phi chips with a total of 3.1 million cores
- IBM Parallel Environment
- Anton
Usage
The slurm system has three main parts:
slurmctld, a central control daemon running on a single control node (optionally with failover backups);- Many computing nodes, each with one or more
slurmddaemons; - Clients that connect to the manager node, often with ssh.
- The clients can issue commands to the control daemon, which would accept and divide the workload to the computing daemons.
For clients, the main commands are srun (queue up an interactive job), sbatch (queue up a job), squeue (print the job queue) and scancel (remove a job from the queue).[examples needed]
Jobs can be run in batch mode or interactive mode. For interactive mode, a compute node would start a shell, connects the client into it, and run the job. From there the user may observe and interact with the job while it is running. Usually, interactive jobs are used for initial debugging, and after debugging, the same job would be submitted by sbatch. For a batch mode job, its stdout and stderr outputs are typically directed to text files for later inspection.
