Jump to content

Scheduler Overview (Slurm): Difference between revisions

From HPCwiki
Phase 1 § 4 P1.4.1: trim to overview only — content split into Partitions / Queues, Choosing a node (constraints), Batch Jobs, Interactive Jobs, Cancelling Jobs, Monitoring Jobs (separate pages). This page is now the entry point with QoS overview and topic index. (via update-page on MediaWiki MCP Server)
No edit summary
 
Line 28: Line 28:


Jobs can in principle be restarted and rescheduled if a higher-priority job needs cluster resources, but at the time of writing this preemption is not actually configured.
Jobs can in principle be restarted and rescheduled if a higher-priority job needs cluster resources, but at the time of writing this preemption is not actually configured.
== Fair share ==
One of the jobs of the cluster job scheduler (SLURM) is to distribute the resources among all the user requesting them. Besides trying to fit jobs in nodes where resources are available for a job, it also needs to keep track of how many jobs a user has started, with how much resources.
Otherwise somebody who has a lot of very small jobs can slowly claim the whole cluster whenever there is a resource available for those small jobs, thus blocking jobs of other people that need more resources.
The way it does this, is by using a fair share for every user. If you have used a lot of resources in the past, your next jobs will be less likely to be scheduled than jobs of people who have just started their jobs.
For more info see https://slurm.schedmd.com/fair_tree.html


== Running MPI jobs ==
== Running MPI jobs ==

Latest revision as of 14:25, 6 November 2026

The resource allocation and scheduling software on Anunna is SLURM: Simple Linux Utility for Resource Management. This page is the entry point — most topics have their own page; below is a short summary plus links.

What's on which page

Quality of Service

When submitting a job, you may optionally assign a different Quality of Service (QoS) to it:

#SBATCH --qos=std

The QoS values configured on Anunna:

  • std (priority 10) — the default. Use this unless you have a specific reason to pick another.
  • low (priority 1) — reduced priority, but limited to 8 hours per job so a flood of low-priority jobs cannot lock up the cluster.
  • high (priority 20) — higher priority than std. More expensive — see Tariffs.
  • interactive (priority 100) — the highest priority, exclusively for immediate-running interactive jobs. You may not submit many or large jobs at this QoS.

Jobs can in principle be restarted and rescheduled if a higher-priority job needs cluster resources, but at the time of writing this preemption is not actually configured.

Fair share

One of the jobs of the cluster job scheduler (SLURM) is to distribute the resources among all the user requesting them. Besides trying to fit jobs in nodes where resources are available for a job, it also needs to keep track of how many jobs a user has started, with how much resources.

Otherwise somebody who has a lot of very small jobs can slowly claim the whole cluster whenever there is a resource available for those small jobs, thus blocking jobs of other people that need more resources.

The way it does this, is by using a fair share for every user. If you have used a lot of resources in the past, your next jobs will be less likely to be scheduled than jobs of people who have just started their jobs.

For more info see https://slurm.schedmd.com/fair_tree.html

Running MPI jobs

For multi-node MPI workloads see MPI on Anunna.

See also