Slurm partitions¶
The Slurm partition setup of LUMI prioritizes jobs that aim to scale out. As a consequence most nodes are reserved for jobs that use all available resources within a node. However, some nodes are reserved for smaller allocations and debugging.
A list of the available partitions can be obtained using the sinfo command.
To get a shorter summary, use sinfo -s.
Slurm partitions allocatable by node¶
The following partitions are available for allocation by node. When using these partitions, your jobs use all resources available on the node and won't share the node with other jobs. Therefore, make sure that your application can take advantage of all the resources on the node as you will be billed for the complete node regardless of the resource actually used as detailed in the billing policy.
The partitions you can use depend on who allocated your project. If your project
was allocated by the EuroHPC-JU, you only have access to the partition whose
names start with ju. If your project was allocated by one of the LUMI
consortium countries, your access is limited to partition with a name that does
not start with ju.
The tables below provide details of the partitions you can have access to depending of your resource allocator:
| Name | Max walltime | Max jobs | Max resources/job | Hardware partition used |
|---|---|---|---|---|
| ju-standard-g | 2 days | 105 (100 running) | 512 nodes | LUMI-G |
| ju-standard | 2 days | 60 ( 50 running) | 256 nodes | LUMI-C |
| ju-strategic-g | 7 days | 105 (100 running) | 404 nodes | LUMI-G |
| ju-strategic | 2 days | 60 ( 50 running) | 256 nodes | LUMI-C |
| bench | 1 day | n/a | All nodes | LUMI-C and LUMI-G |
The bench partition is not available by default and is reserved for
large-scale benchmark runs. Projects wishing to have access to this partition
must send a request to the User Support Team.
Slurm partitions allocatable by resources¶
The following partitions are available for allocation by resources. This means that you can request a sub-node allocation: you can request only part of the resources (cores, gpus, and memory) available on the compute node. This also means that your job may share the node with other jobs.
| Name | Max walltime | Max jobs | Max resources/job | Hardware partition used |
|---|---|---|---|---|
| dev-g | 3 hours | 2 (1 running) | 32 nodes | LUMI-G |
| debug | 30 minutes | 2 (1 running) | 4 nodes | LUMI-C |
| small-g | 3 days | 210 (200 running) | 4 nodes | LUMI-G |
| small | 3 days | 220 (200 running) | 4 nodes | LUMI-C |
| largemem | 1 day | 30 (20 running) | 1 nodes | LUMI-D |
LUMI-C/LUMI-D Large Memory Nodes
The LUMI-C large memory nodes (512GB and 1TB) are located in the
small partition. Therefore, in order to use these nodes, you need to
select the small partition (--partion=small). Then the LUMI-C large
memory nodes will be allocated if you request more memory than is available
in the LUMI-C standard compute nodes.
The nodes in the largemem partition are part of LUMI-D and have
4TB of memory per node.
Getting information about Slurm partitions¶
If you want more precise information about a particular partition, you can use the following command:
The output of this command will give you information about the defaults and
limits which applies to the <partition-name> partition.