Available SLURM clusters
|Parallel resources (policies)|
|mpp2||MPI or shared memory programs on the MPP FDR14 Infiniband cluster "CooLMUC-2"|
|MPI or shared memory programs on the KNL Omnipath cluster "CooLMUC-3". Note that interactive testing is dispatched to a subset of 8 nodes in the same cluster.|
|ivymuc||MPI or shared memory programs on the MPP FDR14 Ivy Bridge based Infiniband cluster|
MPI or shared memory jobs on the 10G Myrinet cluster. For this cluster, it makes sense to specify the partition. Available partitions are:
|inter||Interactive parallel jobs. Which of the clusters is used depends on the login node.|
|tum_chem||Parallel job processing dedicated to TUM chemistry users|
|hm_mech||Parallel job processing dedicated to Hochschule München / Mechatronik users|
|Serial resources (policies)|
For serial job processing. Available partitions are:
Interactive or batch shared memory jobs for high memory requirements (beyond 1 TByte) executed on teramem1.
Serial job processing dedicated to users of BSB
Serial job processing dedicated to users of TUM / geodesy
Serial job processing dedicated to users of the Arnold-Sommerfeld-Centre
This section describes additional features that can be requested via the -C (or --constraint=) option for a job. Note that only values can be specified here; using contradictory values may result in undesired behaviour.
|Purpose of feature||Value to be specified||Effect|
|Select cluster mode||quad||"quadrant"; affinity between cache management and memory. Recommended for everyday use. In certain shared memory model workloads where application can use all the cores in a single process using a threading library like OpenMP and TBB, this mode can also provide better performance than Sub-NUMA clustering mode.|
|Select cluster mode||snc4||"Sub-NUMA clustering"; affinity between tiles, cache management and memory. NUMA-optimized software can profit from this mode. This mode is suitable for distributed memory programming models using MPI or hybrid MPI-OpenMP. Proper pinning of tasks and threads is essential|
|Select cluster mode||a2a||"alltoall"; no affinity between tiles, cache management and memory. Not recommended because performance is degraded|
|Select memory mode||flat|
High bandwidth memory is operated as regular memory mapped into the address space. Note: due to SLURM limitations, the maximum available memory per node for a job will still only be 96 GBytes. The usage of "numactl -p" or Memkind library is recommended.
|Select memory mode||cache|
High bandwidth memory is operated as cache to DDR memory.
|Select memory mode||hybrid|
High bandwidth memory is evenly split between regular memory (8GB) and cache (8 GB)
For details see: KNL Processor Modes