Jump to content

Scheduler Overview (Slurm): Difference between revisions

From HPCwiki
Hjmegens (talk | contribs)
No edit summary
No edit summary
 
(115 intermediate revisions by 9 users not shown)
Line 1: Line 1:
== submitting jobs: sbatch ==
The resource allocation and scheduling software on Anunna is [http://en.wikipedia.org/wiki/Simple_Linux_Utility_for_Resource_Management SLURM]: '''S'''imple '''L'''inux '''U'''tility for '''R'''esource '''M'''anagement. This page is the entry point — most topics have their own page; below is a short summary plus links.


Consider this simple python3 script that should calculate Pi up to 1 million digits:
== What's on which page ==
<source lang='python'>
from decimal import *
D=Decimal
getcontext().prec=10000000
p=sum(D(1)/16**k*(D(4)/(8*k+1)-D(2)/(8*k+4)-D(1)/(8*k+5)-D(1)/(8*k+6))for k in range(411))
print(str(p)[:10000002])
</source>


In order for this script to run, the first thing that is needed is that Python3, which is not the default Python version on the cluster, is load into your environment. Availability of (different versions of) software can be checked by the following command:
* [[Partitions / Queues]] — list of partitions (<code>main</code>, <code>gpu</code>, <code>gpu_amd</code>) and how to choose one.
  module avail
* [[Choosing a node (constraints)]] — defaults, hardware constraints, GPU selection.
* [[Batch Jobs]] — writing sbatch scripts and submitting them, including multi-job submissions and dependencies.
* [[Interactive Jobs]] — <code>sinteractive</code> and <code>salloc</code> for live shell sessions on a compute node.
* [[Array jobs]] — running the same script many times with a varying parameter.
* [[Monitoring Jobs]] — <code>squeue</code>, <code>scontrol</code>, <code>sstat</code>, <code>sacct</code>, <code>node_usage_graph</code>.
* [[Cancelling Jobs]] — <code>scancel</code>.
* [[Reservations]] — booking nodes in advance for events.


In the list you should note that python3 is indeed available to be loaded, which then can be loaded with the following command:
== Quality of Service ==
  module load python/3.3.3


The following shell/slurm script can then be used to schedule the job using the sbatch command:
When submitting a job, you may optionally assign a different Quality of Service (QoS) to it:
<source lang='bash'>
#!/bin/bash
# #SBATCH --time=100
#SBATCH --ntasks=1
#SBATCH --output=output_%j.txt
#SBATCH --error=error_output_%j.txt
#SBATCH --job-name=calc_pi.py
#SBATCH --partition=research


time python3 calc_pi.py
<syntaxhighlight lang="bash">
</source>
#SBATCH --qos=std
</syntaxhighlight>


<source lang='bash'>
The QoS values configured on Anunna:
sbatch run_calc_pi.sh
</source>


  JOBID PARTITION    NAME    USER  ST      TIME  NODES NODELIST(REASON)
* '''std''' (priority 10) — the default. Use this unless you have a specific reason to pick another.
  3347  research calc_pi. megen002  R      0:03      1 node049
* '''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 <code>std</code>. 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.


== allocating resources interactively: sallocate ==
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.


== running MPI jobs on B4F cluster ==
== 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.


== monitoring submitted jobs: squeue ==
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.


== removing jobs from a list: scancel ==
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.


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


== external links ==
== Running MPI jobs ==
 
For multi-node MPI workloads see [[MPI on B4F cluster | MPI on Anunna]].
 
== See also ==
 
* [[Partitions / Queues]]
* [[Choosing a node (constraints)]]
* [[Batch Jobs]]
* [[Interactive Jobs]]
* [[Array jobs]]
* [[Monitoring Jobs]]
* [[Cancelling Jobs]]
* [[Reservations]]
* [[Tariffs | Costs associated with resource usage]]
 
== External links ==
 
* [http://slurm.schedmd.com Slurm official documentation]
* [http://en.wikipedia.org/wiki/Simple_Linux_Utility_for_Resource_Management Slurm on Wikipedia]

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