Last modified by Thomas Coelho (local) on 2023/08/28 15:17

SLURM is the Simple Linux Utility for Resource Management and is an open source, fault-tolerant, and highly scalable cluster management and job scheduling system for large and small Linux clusters.

Slurm is fully integrated in our system. You do not need set any environment variables.


A partition is a subset of the cluster, a bundle of compute nodes with the same characteristics.

Based on access restrictions our cluster is divided in different partitions. 'sinfo' will only show partitions you are allowed to use. Using 'sinfo -a' shows all partitons.

A partition is selected by '-p PARTITIONNAME'.

Partition No. Nodes Cores/M Tot. CoresRAM/GB CPU Remark/Restriction
itp 1020 20064 Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHzCommon Usage
dfg-big332961288-Core AMD Opteron(tm) Processor 6128Group Valenti
dfg-big348144128/25612-Core AMD Opteron(tm) Processor 6168Group Valenti
dfg-big464256128/25616-Core AMD Opteron(tm) Processor 6272Group Valenti
dfg-big448192128/25612-Core AMD Opteron(tm) Processor 6344Group Valenti
fplo21224256Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHzGroup Valenti
fplo41632256Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHzGroup Valenti
dfg-xeon51632128Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHzGroup Valenti
dfg-xeon720140128Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHzGroup Valenti
iboga342088064Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHzGroup Rezzolla
dreama140401024Intel(R) Xeon(R) CPU E7-4820 v3 @ 1.90GHzGroup Rezzolla
barcelona840320192Intel(R) Xeon(R) Gold 6148 CPU @ 2.40GHz

Group Valenti


Intel(R) Xeon(R) Silver 4316 CPU @ 2.30GHz

Group Valenti
mallorca448192256AMD EPYC 7352 24-Core ProcessorGroup Valenti
calea36642304256Intel(R) Xeon(R) Platinum 8358 CPU @ 2.60GHz

Group Rezzolla

majortom16464256AMD EPYC 7513 32-Core ProcessorGroup Bleicher

Most nodes are for exclusive use by their corresponding owners. The itp nodes are for common usage. Except for 'fplo' and 'dfg-big' nodes, all machines are connected with Infiniband for all traffic (IP and internode communitcation - MPI)

Submitting Jobs

In most cases you want to submit a non interactive job to be executed in our cluster.

This is very simple for serial (1 CPU) jobs:

  sbatch -p PARTITION

where is a shell script with your job commands.

Running openMPI jobs is not much more complictated:

  sbatch -p PARTITION -n X

where X is the number of desired MPI processes. Launch the job in the jobscript with:


You don't have to worry about the number of processes or specific nodes. Both slurm and openmpi know
about each other.

Running SMP jobs (multiple threads, not necessary mpi). Running MPI jobs on a single node is recommended for the

dfg-big nodes. This are big host with up to 64 cpu's per node, but 'slow' gigabit network connection. Launch SMP jobs with

  sbatch -p PARTITION -N 1 -n X

Differences in network the network connection

The new v3 dfg-xeon nodes are equipped with 10 GB network. This is faster (trough put) and has lower latency then gigabit ethernet, but is not is not as fast as the DDR infinband network. The 10 GB network is used for MPI and I/O. Infiniband is only use for MPI.

Defining Resource limits

By default each job allocates 2 GB memory and a run time of 3 days. More resources can be requested by


where <MB> is the memory in megabytes. The virtual memory limit is 2.5 times of the requested real memory limit.

The memory limit is not a hard limit. When exceeding the limit, your memory will be swapped out. Only when using more the 110% of the limit your job will be killed. So be conservative, to keep enough room for other jobs. Requested memory is blocked from the use by other jobs.

  -t or --time=<time>

where time can be set in the format "days-hours". See man page for more formats.

Memory Management

In Slurm you specify only one parameter, which is the limit for your real memory usage and drives the decision where your job is started. The virtual memory of your job maybe 2.5 times of your requested memory. You can exceed your memory limit by 20%. But this will be swap space instead of real memory. This prevents crashing if you memory limit is a little to tight.

Inline Arguments

sbatch arguments can be written in the jobfile:

#! /bin/bash
# Choosing a partition:
#SBATCH -p housewives