Changes

Jump to: navigation, search

Humus

997 bytes added, 15:26, October 23, 2023
Job scheduling
=== Job scheduling ===
You can, if you wish, submit We recommend using batch jobs for your work whenever feasible, using the Slurm job scheduler. This allows you to queue up several tasks which will execute one after another without constant human supervision.It also allows group members to share the resources more effectively,'e.g.' the scheduler will not try to run two different jobs that both need a GPUon the same node at the same time; it will either run them on different nodesor at different times. 
The Humus nodes carry NVidia A30 GPUs, so the following command will run `jobscript`
on one entire node:
sbatch --time=6:0:0 --gres=gpu:a30:1 --cpus-per-task=64 --mem=0 jobscript
 
If the data resides on (for example) humus217 but not on humus216,
you should specify which node the job should execute on with `--nodelist`.
Don't omit to specify the CPU, GPU and memory you need though! For example:
sbatch --nodelist=humus217 --time=6:0:0 --gres=gpu:a30:1 --cpus-per-task=64 --mem=0 jobscript
 
If you do not need the GPU for a certain calculation, or you need less than
an entire node's CPUs and memory, please specify only what you need.
The scheduler can run more than one such job on the node at a time. For example:
sbatch --time=24:0:0 --cpus-per-task=1 --mem=4G jobscript

Navigation menu