Content

Code execution

For examples for code execution, please visit CPU Genoa partition.

Code compilation

For code compilation please use gnu compiler.

MPI, gnu

module load gcc/13.3.0
module load openmpi/gcc/5.0.3
mpicc -Wl,-rpath,$LD_RUN_PATH -o hello.bin hello.c

MPI, OpenMP, gnu

module load gcc/13.3.0
module load openmpi/gcc/5.0.3
mpicc -fopenmp -Wl,-rpath,$LD_RUN_PATH -o hello.bin hello.c

Slurm job script

A slurm script is submitted to the job scheduler slurm. It contains

the request for compute nodes of a CPU Genoa partition and
commands to start your binary. You have two options to start an MPI binary.
- using srun (recommended when using Open MPI)
- using mpirun

Using srun

When using Open MPI on the CPU Genoa partitions, you can make benefit of Open MPIs support for Slurm. Resource specifications provided in batch jobs or job steps (srun), such as number of tasks etc, are understood by the MPI library.

MPI, full node

#!/bin/bash
#SBATCH --nodes=2
#SBATCH --partition=cpu-genoa
#SBATCH --ntasks-per-node=192

srun ./hello.bin

You can also run hybrid codes, i.e. applications using both MPI and OpenMP. The example covers the setup

2 nodes
8 (MPI) processes per node, 24 (OpenMP) threads per process.

Note that

MPI, OpenMP, full node

#!/bin/bash
#SBATCH --partition=cpu-genoa
#SBATCH --nodes=2
#SBATCH --ntasks-per-node=8
#SBATCH --cpus-per-task=24
# to avoid usage of Hyperthreads
#SBATCH --hint=nomultithread

# Set number of OpenMP threads to the same of number cpus per task requested from slurm
export OMP_NUM_THREADS=${SLURM_CPUS_PER_TASK}

# Ensure proper binding of OpenMP threads
export OMP_PROC_BIND=true
export OMP_PLACES=cores

srun ./hello.bin

Using mpirun

With mpirun, you can manipulate the the process binding, mapping and ranking with the command its line arguments. Refer to the man page of the respective MPI library for details.