Introduction to Slurm¶
The batch system used at UPPMAX, HPC2N, LUNARC, NSC, PDC, C3SE (and most other HPC centres in Sweden) is called Slurm.
Guides and documentation
- HPC2N: https://docs.hpc2n.umu.se/documentation/batchsystem/intro/
- UPPMAX: https://docs.uppmax.uu.se/cluster_guides/slurm/
- LUNARC: https://lunarc-documentation.readthedocs.io/en/latest/manual/manual_intro/
- NSC: https://www.nsc.liu.se/support/batch-jobs/introduction/
- PDC: https://support.pdc.kth.se/doc/run_jobs/job_scheduling/
- C3SE: https://www.c3se.chalmers.se/documentation/submitting_jobs/
Slurm is an Open Source job scheduler, which provides three key functions:
- Keeps track of available system resources - it allocates to users, exclusive or non-exclusive access to resources for some period of time
- Enforces local system resource usage and job scheduling policies - provides a framework for starting, executing, and monitoring work
- Manages a job queue, distributing work across resources according to policies
Slurm is designed to handle thousands of nodes in a single cluster, and can sustain throughput of 120,000 jobs per hour.
You can run programs either by giving all the commands on the command line or by submitting a job script.
Using a job script is often recommended:
- If you ask for the resources on the command line, you will wait for the program to run before you can use the window again (unless you can send it to the background with
&). - If you use a job script you have an easy record of the commands you used, to reuse or edit for later use.
In order to run a batch job, you need to create and submit a SLURM submit file (also called a batch submit file, a batch script, or a job script).
Slurm commands¶
There are many more commands than the ones we have chosen to look at here, but these are the most commonly used ones. You can find more information on the Slurm homepage: Slurm documentation.
- salloc: requesting an interactive allocation
- interactive: another way of requesting an interactive allocation
- sbatch: submitting jobs to the batch system
- squeue: viewing the state of the batch queue
- scancel: cancel a job
- scontrol show: getting more info on jobs, nodes
- sinfo: information about the partitions/queues
Let us look at these one at a time.
salloc and interactive¶
This is for requesting an interactive allocation. This is done differently depending on the centre.
| Cluster | interactive | salloc | srun | GfxLauncher or OpenOnDemand |
|---|---|---|---|---|
| HPC2N | Works | Recommended | N/A | Recommended (OOD) |
| UPPMAX | Recommended | Works | N/A | N/A |
| LUNARC | Works | N/A | N/A | Recommended (GfxLauncher) |
| NSC | Recommended | N/A | N/A | N/A |
| PDC | N/A | Recommended | N/A | Possible |
| C3SE | N/A | N/A | Works | Recommended (OOD) |
Examples¶
interactive
This is recommended at UPPMAX and NSC, and works at HPC2N and LUNARC.
Usage: interactive -A [project_name]
If you want longer walltime, more CPUs/GPUs, etc. you need to ask for that as well. This is the default which gives 1 CPU for 1 hour.
[bbrydsoe@rackham3 ~]$ interactive -A uppmax2025-2-296
You receive the high interactive priority.
You may run for at most one hour.
Your job has been put into the devcore partition and is expected to start at once.
(Please remember, you may not simultaneously have more than one devel/devcore job, running or queued, in the batch system.)
Please, use no more than 6.4 GB of RAM.
salloc: Pending job allocation 55388069
salloc: job 55388069 queued and waiting for resources
salloc: job 55388069 has been allocated resources
salloc: Granted job allocation 55388069
salloc: Waiting for resource configuration
salloc: Nodes r483 are ready for job
_ _ ____ ____ __ __ _ __ __
| | | | _ \| _ \| \/ | / \ \ \/ / | System: r483
| | | | |_) | |_) | |\/| | / _ \ \ / | User: bbrydsoe
| |_| | __/| __/| | | |/ ___ \ / \ |
\___/|_| |_| |_| |_/_/ \_\/_/\_\ |
###############################################################################
User Guides: https://docs.uppmax.uu.se/
Write to support@uppmax.uu.se, if you have questions or comments.
[bbrydsoe@r483 ~]$
[x_birbr@tetralith3 ~]$ interactive -A naiss2025-22-403
salloc: Pending job allocation 44252533
salloc: job 44252533 queued and waiting for resources
salloc: job 44252533 has been allocated resources
salloc: Granted job allocation 44252533
salloc: Waiting for resource configuration
salloc: Nodes n340 are ready for job
[x_birbr@n340 ~]$
salloc
This is recommended at HPC2N and PDC, and works at UPPMAX.
Usage: salloc -A [project_name] -t HHH:MM:SS
You have to give project ID and walltime. If you need more CPUs (1 is default) or GPUs, you have to ask for that as well.
At PDC, you also have to give the partition: main, shared, gpu
b-an01 [~]$ salloc -A hpc2n2025-076 -t 00:10:00
salloc: Pending job allocation 34624444
salloc: job 34624444 queued and waiting for resources
salloc: job 34624444 has been allocated resources
salloc: Granted job allocation 34624444
salloc: Nodes b-cn1403 are ready for job
b-an01 [~]$
WARNING! This is not true interactivity! Note that we are still on the login node!
In order to run anything in the allocation, you need to preface with srun like this:
Otherwise anything will run on the login node! Also, interactive sessions (for instance a program that asks for input) will not work correctly as that dialogoue happens on the compute node which you do not have real access to!
bbrydsoe@login1:~> salloc --time=00:10:00 -A naiss2025-22-403 -p main
salloc: Pending job allocation 9722449
salloc: job 9722449 queued and waiting for resources
salloc: job 9722449 has been allocated resources
salloc: Granted job allocation 9722449
salloc: Waiting for resource configuration
salloc: Nodes nid001134 are ready for job
bbrydsoe@login1:~>
Again, you are on the login node, and anything you want to run in the allocation must be preface with srun.
However, at PDC you have another option; you can ssh to the allocated compute node and then it will be true interactivity:
srun
This works at C3SE, but is not recommended as when the login node is restarted the interactive job is also terminated.
GfxLauncher and OpenOnDemand
This is recommended at HPC2N, LUNARC, and C3SE, and is possible at PDC.
- Go to https://portal.hpc2n.umu.se/ and login.
- Documentation here: https://docs.hpc2n.umu.se/tutorials/connections/#open__ondemand
- Login with ThinLinc: https://lunarc-documentation.readthedocs.io/en/latest/getting_started/using_hpc_desktop/
- Follow the documentation for starting the GfxLauncher for OpenOnDemand: https://lunarc-documentation.readthedocs.io/en/latest/getting_started/gfxlauncher/
- Go to https://alvis.c3se.chalmers.se/
- There is some documentation here: https://uppmax.github.io/HPC-python/common/interactive_ondemand.html#start-an-interactive-session-from-ondemand
sbatch¶
The command sbatch is used to submit jobs to the batch system.
This is done from the command line in the same way at all the HPC centres in Sweden:
For any .sbatch or .sh, but it is not a requirement. You can use any or no suffix. It is merely to make it easier to find the script among the other files.
Note
- At centres that have OpenOnDemand installed, you do not have to submit a batch job, but can run directly on the already allocated resources (see interactive jobs).
- OpenOnDemand is a good option for interactive tasks, graphical applications/visualization, and simpler job submittions. It can also be more user-friendly.
- Regardless, there are many situations where submitting a batch job is the best option instead, including when you want to run jobs that need many resources (time, memory, multiple cores, multiple GPUs) or when you run multiple jobs concurrently or in a specified succession, without need for manual intervention. Batch jobs are often also preferred for automation (scripts) and reproducibility. Many types of application software fall into this category.
- At centres that have ThinLinc you can usually submit MATLAB jobs to compute resources from within MATLAB.
We will talk much more about batch scripts in a short while, but for now we can use this small batch script for testing the Slurm commands:
#!/bin/bash
# Project id - change to your own!
#SBATCH -A PROJ-ID
# Asking for 1 core
#SBATCH -n 1
# Asking for a walltime of 1 min
#SBATCH --time=00:01:00
echo "What is the hostname? It is this: "
/bin/hostname
Example:
Submitting the above batch script on Tetralith (NSC)
As you can see, you get the job id when submitting the batch script.
When it has run, you can see with ls that you got a file called slurm-JOBID.out in your directory.
squeue¶
The command squeue is for viewing the state of the batch queue.
If you just give the command, you will get a long list of all jobs in the queue, so it is usually best to constrain it to your own jobs. This can be done in two ways:
squeue -u <username>squeue --me
Example:
b-an01 [~]$ squeue --me
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
34815904 cpu_sky mpi_gree bbrydsoe R 0:00 1 b-cn1404
34815905 cpu_sky mpi_hell bbrydsoe R 0:00 2 b-cn[1404,1511]
34815906 cpu_sky mpi_hi.s bbrydsoe R 0:00 2 b-cn[1511-1512]
34815907 cpu_sky simple.s bbrydsoe R 0:00 1 b-cn1512
34815908 cpu_sky compiler bbrydsoe R 0:00 2 b-cn[1415,1512]
34815909 cpu_sky mpi_gree bbrydsoe R 0:00 1 b-cn1415
34815910 cpu_sky mpi_hell bbrydsoe R 0:00 3 b-cn[1415,1421-1422]
34815911 cpu_sky mpi_hi.s bbrydsoe R 0:00 1 b-cn1422
34815912 cpu_sky simple.s bbrydsoe R 0:00 1 b-cn1422
34815913 cpu_sky compiler bbrydsoe R 0:00 2 b-cn[1422,1427]
34815902 cpu_zen4 simple.s bbrydsoe CG 0:03 1 b-cn1707
34815903 cpu_zen4 compiler bbrydsoe R 0:00 1 b-cn1708
34815898 cpu_zen4 compiler bbrydsoe R 0:03 2 b-cn[1703,1705]
34815899 cpu_zen4 mpi_gree bbrydsoe R 0:03 2 b-cn[1705,1707]
34815900 cpu_zen4 mpi_hell bbrydsoe R 0:03 1 b-cn1707
34815901 cpu_zen4 mpi_hi.s bbrydsoe R 0:03 1 b-cn1707
34815922 cpu_zen4, simple.s bbrydsoe PD 0:00 1 (Priority)
34815921 cpu_zen4, mpi_hi.s bbrydsoe PD 0:00 1 (Priority)
34815920 cpu_zen4, mpi_hell bbrydsoe PD 0:00 1 (Priority)
34815919 cpu_zen4, mpi_gree bbrydsoe PD 0:00 1 (Priority)
34815918 cpu_zen4, compiler bbrydsoe PD 0:00 1 (Priority)
34815917 cpu_zen4, simple.s bbrydsoe PD 0:00 1 (Priority)
34815916 cpu_zen4, mpi_hi.s bbrydsoe PD 0:00 1 (Priority)
34815915 cpu_zen4, mpi_hell bbrydsoe PD 0:00 1 (Priority)
34815914 cpu_zen4, mpi_gree bbrydsoe PD 0:00 1 (Resources)
Here you also see some of the “states” a job can be in. Some of the more common ones are:
- CA: CANCELLED. Job was explicitly cancelled by the user or system administrator.
- CF: CONFIGURING. Job has been allocated resources, but are waiting for them to become ready for use (e.g. booting).
- CG: COMPLETING. Job is in the process of completing. Some processes on some nodes may still be active.
- PD: PENDING. Job is awaiting resource allocation.
- R: RUNNING. Job currently has an allocation.
- S: SUSPENDED. Job has an allocation, but execution has been suspended and resources have been released for other jobs.
List above from Slurm workload manager page about squeue.
Example:
Submit the “simple.sh” script several times, then do squeue --me to see that it is running, pending, or completing.
[x_birbr@tetralith3 ~]$ sbatch simple.sh
Submitted batch job 45194596
[x_birbr@tetralith3 ~]$ sbatch simple.sh
Submitted batch job 45194597
[x_birbr@tetralith3 ~]$ sbatch simple.sh
Submitted batch job 45194598
[x_birbr@tetralith3 ~]$ sbatch simple.sh
Submitted batch job 45194599
[x_birbr@tetralith3 ~]$ sbatch simple.sh
Submitted batch job 45194600
[x_birbr@tetralith3 ~]$ sbatch simple.sh
Submitted batch job 45194601
[x_birbr@tetralith3 ~]$ sbatch simple.sh
Submitted batch job 45194602
[x_birbr@tetralith3 ~]$ sbatch simple.sh
Submitted batch job 45194603
[x_birbr@tetralith3 ~]$ squeue --me
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
45194603 tetralith simple.s x_birbr PD 0:00 1 (None)
45194602 tetralith simple.s x_birbr PD 0:00 1 (None)
45194601 tetralith simple.s x_birbr PD 0:00 1 (None)
45194600 tetralith simple.s x_birbr PD 0:00 1 (None)
45194599 tetralith simple.s x_birbr PD 0:00 1 (None)
45194598 tetralith simple.s x_birbr PD 0:00 1 (None)
45194597 tetralith simple.s x_birbr PD 0:00 1 (None)
45194596 tetralith simple.s x_birbr PD 0:00 1 (None)
scancel¶
The command to cancel a job is scancel.
You can either cancel a specific job:
scancel <job id>
or cancel all your jobs:
scancel -u <username>
Note
As before, you get the <job id> either from when you submitted the job or from squeue --me.
Note
Only administrators can cancel other people’s jobs!
scontrol show¶
The command scontrol show is used for getting more info on jobs and nodes.
scontrol show job¶
As usual, you get the <job id> from either when you submit the job or from squeue --me.
The command is:
Example:
b-an01 [~]$ scontrol show job 34815931
JobId=34815931 JobName=compiler-run
UserId=bbrydsoe(2897) GroupId=folk(3001) MCS_label=N/A
Priority=2748684 Nice=0 Account=staff QOS=normal
JobState=COMPLETED Reason=None Dependency=(null)
Requeue=0 Restarts=0 BatchFlag=1 Reboot=0 ExitCode=0:0
RunTime=00:00:07 TimeLimit=00:10:00 TimeMin=N/A
SubmitTime=2025-06-24T11:36:32 EligibleTime=2025-06-24T11:36:32
AccrueTime=2025-06-24T11:36:32
StartTime=2025-06-24T11:36:32 EndTime=2025-06-24T11:36:39 Deadline=N/A
SuspendTime=None SecsPreSuspend=0 LastSchedEval=2025-06-24T11:36:32 Scheduler=Main
Partition=cpu_zen4 AllocNode:Sid=b-an01:626814
ReqNodeList=(null) ExcNodeList=(null)
NodeList=b-cn[1703,1705]
BatchHost=b-cn1703
NumNodes=2 NumCPUs=12 NumTasks=12 CPUs/Task=1 ReqB:S:C:T=0:0:*:*
ReqTRES=cpu=12,mem=30192M,node=1,billing=12
AllocTRES=cpu=12,mem=30192M,node=2,billing=12
Socks/Node=* NtasksPerN:B:S:C=0:0:*:* CoreSpec=*
MinCPUsNode=1 MinMemoryCPU=2516M MinTmpDiskNode=0
Features=(null) DelayBoot=00:02:00
OverSubscribe=OK Contiguous=0 Licenses=(null) Network=(null)
Command=/pfs/proj/nobackup/fs/projnb10/support-hpc2n/bbrydsoe/intro-course/hands-ons/3.usage/compile-run.sh
WorkDir=/pfs/proj/nobackup/fs/projnb10/support-hpc2n/bbrydsoe/intro-course/hands-ons/3.usage
StdErr=/pfs/proj/nobackup/fs/projnb10/support-hpc2n/bbrydsoe/intro-course/hands-ons/3.usage/slurm-34815931.out
StdIn=/dev/null
StdOut=/pfs/proj/nobackup/fs/projnb10/support-hpc2n/bbrydsoe/intro-course/hands-ons/3.usage/slurm-34815931.out
Power=
Here you get much interesting information:
- JobState=COMPLETED: the job was completed and was not FAILED. It could also have been PENDING or COMPLETING
- RunTime=00:00:07: the job ran for 7 seconds
- TimeLimit=00:10:00: It could have run for up to 10 min (what you asked for)
- SubmitTime=2025-06-24T11:36:32: when your job was submitted
- StartTime=2025-06-24T11:36:32: when the job started
- Partition=cpu_zen4: what partition/type of node it ran on
- NodeList=b-cn[1703,1705]: which specific nodes it ran on
- BatchHost=b-cn1703: which of the nodes (if several) that was the master
- NumNodes=2 NumCPUs=12 NumTasks=12 CPUs/Task=1: number of nodes, cpus, tasks
- WorkDir=/pfs/proj/nobackup/fs/projnb10/support-hpc2n/bbrydsoe/intro-course/hands-ons/3.usage: which directory your job was submitted from/was running in
- StdOut=/pfs/proj/nobackup/fs/projnb10/support-hpc2n/bbrydsoe/intro-course/hands-ons/3.usage/slurm-34815931.out: which directory the output files will be placed in
The command scontrol show job <job id> can be run also while the job is pending, and can be used to get an estimate of when the job will start. Actual start time depends on the jobs priority, any other (people’s) jobs starting and completing and being submitted, etc.
It is often useful to know which nodes a job ran on if something did not work - perhaps the node was faulty.
scontrol show node¶
This command is used to get information about a specific node. You can for instance see its features, how many cores per socket, uptime, etc. Specifics will vary and depend on the centre you are running jobs at.
Example:
This if for one of the AMD Zen4 nodes at Kebnekaise, HPC2N.
b-an01 [~]$ scontrol show node b-cn1703
NodeName=b-cn1703 Arch=x86_64 CoresPerSocket=128
CPUAlloc=253 CPUEfctv=256 CPUTot=256 CPULoad=253.38
AvailableFeatures=rack17,amd_cpu,zen4
ActiveFeatures=rack17,amd_cpu,zen4
Gres=(null)
NodeAddr=b-cn1703 NodeHostName=b-cn1703 Version=23.02.7
OS=Linux 5.15.0-142-generic #152-Ubuntu SMP Mon May 19 10:54:31 UTC 2025
RealMemory=644096 AllocMem=636548 FreeMem=749623 Sockets=2 Boards=1
State=MIXED ThreadsPerCore=1 TmpDisk=0 Weight=100 Owner=N/A MCS_label=N/A
Partitions=cpu_zen4
BootTime=2025-06-24T06:32:25 SlurmdStartTime=2025-06-24T06:37:02
LastBusyTime=2025-06-24T08:29:45 ResumeAfterTime=None
CfgTRES=cpu=256,mem=629G,billing=256
AllocTRES=cpu=253,mem=636548M
CapWatts=n/a
CurrentWatts=0 AveWatts=0
ExtSensorsJoules=n/s ExtSensorsWatts=0 ExtSensorsTemp=n/s
sinfo¶
The command sinfo gives you information about the partitions/queues.
Example:
This is for Tetralith, NSC
[x_birbr@tetralith3 ~]$ sinfo
PARTITION AVAIL TIMELIMIT NODES STATE NODELIST
tetralith* up 7-00:00:00 1 plnd n1541
tetralith* up 7-00:00:00 16 drain* n[237,245,439,532,625,646,712,759-760,809,1290,1364,1455,1638,1847,1864]
tetralith* up 7-00:00:00 3 drain n[13,66,454]
tetralith* up 7-00:00:00 20 resv n[1-4,108,774,777,779-780,784-785,788,1109,1268,1281-1285,1288]
tetralith* up 7-00:00:00 327 mix n[7,39-40,46,50,69-70,75,78,85,91-93,97,112,119,121,124,126,128,130-134,137,139,141,149-150,156,159,164,167-168,170,174,184,187-188,190,193,196,203,206,208,212,231,241,244,257,259,262,267,280,287,293-294,310,315,323,327,329,333,340,350,352,371,377,379-381,385,405,420-422,434,441,446,465,467,501,504-505,514,524,529,549,553,558,561,564,573,575,602,610,612,615,617,622-623,626-627,631,637,651,662,671,678,691-692,699,703,709,718,720,723,726,741,745,752,754-755,768,776,781,790,792-793,803-804,808,818,853,855,859,863,867,881,883,915,925,959,966,974,981,984,999,1001-1003,1007-1011,1015,1018,1033,1044-1046,1050-1052,1056-1058,1071,1077,1102,1105-1106,1111-1115,1117,1119,1130,1132,1134-1136,1138-1140,1142-1143,1252,1254,1257,1267,1278-1279,1292,1296,1298,1309,1328,1339,1343,1345,1347,1349,1352,1354-1355,1357,1367,1375-1376,1379,1381,1386-1388,1398,1403,1410,1412,1420-1422,1428,1440,1446,1450,1459,1466,1468-1470,1474,1490-1491,1493,1498,1506,1510,1513,1520,1524,1529,1548-1549,1553,1562,1574-1575,1579,1586,1592,1595,1601,1606,1608,1612,1615,1620-1621,1631,1634,1639,1642,1647,1651-1653,1665,1688,1690,1697,1702,1706,1715-1716,1725,1728,1749,1754,1756,1767,1772,1774-1775,1778,1795-1796,1798-1799,1811,1816,1822,1826,1834,1842,1849,1857-1858,1871,1874,1879,1881,1896,1900,1902,1909,1911-1914,1945,1951,1953,1955-1956,1960,1969,1978,1983,2001,2005-2006,2008]
tetralith* up 7-00:00:00 1529 alloc n[5-6,8-12,14-38,41-45,47-49,51-60,65,67-68,71-74,76-77,79-84,86-90,94-96,98-107,109-111,113-118,120,122-123,125,127,129,135-136,138,140,142-148,151-155,157-158,160-163,165-166,169,171-173,175-183,185-186,189,191-192,194-195,197-202,204-205,207,209-211,213-230,232-236,238-240,242-243,246-256,258,260-261,263-266,268-279,281-286,288-292,295-309,311-314,316-322,324-326,328,330-332,334-339,341-349,351,353-370,372-376,378,382-384,386-404,406-419,423-433,435-438,440,442-445,447-453,455-464,466,468-500,502-503,506-513,515-523,525-528,530-531,533-548,550-552,554-557,559-560,562-563,565-572,574,576-601,603-609,611,613-614,616,618-621,624,628-630,632-636,638-645,647-650,652-661,663-670,672-677,679-690,693-698,700-702,704-708,710-711,713-717,719,721-722,724-725,727-740,742-744,746-751,753,756-758,761-767,769-773,775,778,782-783,786-787,789,791,794-802,805-807,810-817,819-852,854,856-858,860-862,864-866,868-880,882,884-889,893,896-914,916-924,926-937,939-940,943,945,948-958,960-965,967-973,975-980,982-983,985-998,1000,1004-1006,1012-1014,1016-1017,1019-1032,1034-1043,1047-1049,1053-1055,1059-1070,1072-1076,1078-1101,1103-1104,1107-1108,1110,1116,1118,1120-1129,1131,1133,1137,1141,1144,1249-1251,1253,1255-1256,1258-1266,1269-1277,1280,1286-1287,1289,1291,1293-1295,1297,1299-1308,1310-1327,1329-1338,1340-1342,1344,1346,1348,1350-1351,1353,1356,1358-1363,1365-1366,1368-1374,1377-1378,1380,1382-1385,1389-1397,1399-1402,1404-1409,1411,1413-1419,1423-1427,1429-1439,1441-1445,1447-1449,1451-1454,1456-1458,1460-1465,1467,1471-1473,1475-1489,1492,1494-1497,1499-1505,1507-1509,1511-1512,1514-1519,1521-1523,1525-1528,1530-1540,1542-1547,1550-1552,1554-1561,1563-1573,1576-1578,1580-1585,1587-1591,1593-1594,1596-1600,1602-1605,1607,1609-1611,1613-1614,1616-1619,1622-1630,1632-1633,1635-1637,1640-1641,1643-1646,1648-1650,1654-1664,1666-1687,1689,1691-1696,1698-1701,1703-1705,1707-1714,1717-1724,1726-1727,1729-1748,1750-1753,1755,1757-1766,1768-1771,1773,1776-1777,1779-1794,1797,1800-1810,1812-1815,1817-1821,1824-1825,1827-1833,1835-1841,1843-1846,1848,1850-1856,1859-1863,1865-1870,1872-1873,1875-1878,1880,1882-1895,1897-1899,1901,1903-1908,1910,1915-1944,1946-1950,1952,1954,1957-1959,1961-1968,1970-1977,1979-1982,1984-2000,2002-2004,2007,2009-2016]
As you can see, it shows partitions, nodes, and states. State can be drain, idle, resv, alloc, mix, plnd (and a few others), where the exact naming varies between centers.
- drain: node is draining after running a job
- resv: node is reserved/has a reservation for something
- alloc: node is allocated for a job
- mix: node is in several states, could for instance be that it is allocated, but starting to drain
- idle: node is free and can be allocated
- plnd: job planned for a higher priority job
You can see the full list of states and their meaning with man sinfo.
Slurm job scripts¶
Now we have looked at the commands to control the job, it is time to look at the job scripts themselves.
Serial job¶
The simplest example is for a serial job. Here running a small Python script mmmult.py.
#!/bin/bash
#SBATCH -A naiss2025-22-934 # Change to your own
#SBATCH --time=00:10:00 # Asking for 10 minutes
#SBATCH -n 1 # Asking for 1 core
# Load any modules you need, here GCC 11.3.0 and Python 3.10.4
module load buildtool-easybuild/4.8.0-hpce082752a2 GCC/11.3.0 OpenMPI/4.1.4 Python/3.10.4 SciPy-bundle/2022.05
# Run your Python script
python mmmult.py
#!/bin/bash
#SBATCH -A hpc2n2025-151 # Change to your own
#SBATCH --time=00:10:00 # Asking for 10 minutes
#SBATCH -n 1 # Asking for 1 core
# Load any modules you need, here for Python/3.11.3 and compatible SciPy-bundle
module load GCC/12.3.0 Python/3.11.3 SciPy-bundle/2023.07
# Run your Python script
python mmmult.py
#!/bin/bash
#SBATCH -A luXXXX-Y-ZZ # Change to your own
#SBATCH --time=00:10:00 # Asking for 10 minutes
#SBATCH -n 1 # Asking for 1 core
# Load any modules you need, here for Python/3.11.5 and compatible SciPy-bundle
module load GCC/13.2.0 Python/3.11.5 SciPy-bundle/2023.11
# Run your Python script
python mmmult.py
import timeit
import numpy as np
starttime = timeit.default_timer()
np.random.seed(1701)
A = np.random.randint(-1000, 1000, size=(8,4))
B = np.random.randint(-1000, 1000, size =(4,4))
print("This is matrix A:\n", A)
print("The shape of matrix A is ", A.shape)
print()
print("This is matrix B:\n", B)
print("The shape of matrix B is ", B.shape)
print()
print("Doing matrix-matrix multiplication...")
print()
C = np.matmul(A, B)
print("The product of matrices A and B is:\n", C)
print("The shape of the resulting matrix is ", C.shape)
print()
print("Time elapsed for generating matrices and multiplying them is ", timeit.default_timer() - starttime)
You submit the jobscript with sbatch <jobscript.sh> as was mentioned earlier.
Information about jobs¶
Use the following:
- sacct
- job-info