Running Calculations

Description

On your desktop computer, you start your calculations and they start immediately, run until they are finished, then your desktop does mostly nothing, until you start another calculation. A compute cluster has several hundred, maybe a thousand computers (compute nodes), all of them are busy most of the time and many people want to run a great number of calculations. So running your job has to include some extra steps:

1. prepare a script (usually a shell script), with all the commands that are necessary to run your calculation from start to finish. In addition to the commands necessary to run the calculation, this batch script has a header section, in which you specify details like required compute cores, estimated runtime, memory requirements, disk space needed, etc.
2. Submit the script into a queue, where your job (calculation)
3. Job is queued and waits in row with other compute jobs until the resources you requested in the header become available.
4. Execution: Once your job reaches the front of the queue, your script is executed on a compute node. Your calculation runs on that node until it is finished or reaches the specified time limit.
5. Save results: At the end of your script, include commands to save the calculation results back to your home directory.

There are two types of batch systems currently used on bwHPC clusters, called "Moab" (legacy installs) and "Slurm".

Link to Batch System per Cluster

Because of differences in configuration (partly due to different available hardware), each cluster has their own batch system documention:

• Slurm systems
  • Slurm bwUniCluster 2.0
  • Slurm JUSTUS 2
  • Slurm Helix
• Moab systems (legacy systems with deprecated queuing system)
  • Moab NEMO specific information
  • Moab BinAC specific information

Scaling

When you are running your calculations, you will have to decide on how many compute-cores your calculation will be simultaniously calculated. For this, your computational problem will have to be divided into pieces, which always causes some overhead.

How to find a reasonable number of how many compute cores to use for your calculation is described in the page

• Scaling

Energy Efficiency

Please also see our advice for

• Energy Efficient Cluster Usage

HPC Glossary

A short definition of the typical elements of an HPC cluster.

HPC Cluster

Collection of compute nodes with (usually) high bandwidth and low latency communication. They can be accessed via login nodes.

Node

An individual computer with one or more sockets, part of an HPC cluster.

Socket

Physical socket where the CPU capsules are placed.

Core: The physical unit that can independently execute tasks on a CPU. Modern CPUs generally have multiple cores.

Thread: A logical unit that can be executed independently. If the same processor core is configured to execute one or more execution paths in parallel it is called Hyperthreading (a hardware setting). Alternatively, there can be software threads that can be understood in the context of "parallel execution paths" within the same program (eg. to work through different and independent data arrays in parallel). This is referred to as Multithreading, eg. via OpenMP.

CPU: Central Processing Unit. It performs the actual computation in a compute node. A modern CPU is composed of numerous cores and layers of cache.

GPU: Graphics Processing Unit. GPUs in HPC clusters are used as high-performance accelerators and are particularly useful to process workloads in the fields of Machine Learning (ML) and Artificial Intelligence (AI) more efficiently. The software has to be designed specifically to use GPUs. CUDA and OpenACC are the most popular platforms in scientific computing with GPUs.

RAM: Random Access Memory. It is used as the working memory for the cores.

Batch System

incl. Scheduler, Moab, Slurm

Script

Shell Script / Bash

Job