From 98e73c47084ff5764192227ed5f40d4a05defff7 Mon Sep 17 00:00:00 2001 From: Sebastian Doebel <sebastian.doebel@tu-dresden.de> Date: Tue, 16 Apr 2024 11:36:21 +0200 Subject: [PATCH] clean up AlphaCentauri references --- .../docs/jobs_and_resources/slurm_examples.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm_examples.md b/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm_examples.md index 2c00d715b..c05c2da60 100644 --- a/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm_examples.md +++ b/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm_examples.md @@ -146,16 +146,14 @@ This is useful to document the cluster used or avoid accidentally using the wron The number of cores per node that are currently allowed to be allocated for GPU jobs is limited depending on how many GPUs are being requested. -On Alpha Centauri you may only request up to 6 cores per requested GPU. This is because we do not wish that GPUs become unusable due to all cores on a node being used by a single job which does not, at the same time, request all GPUs. E.g., if you specify `--gres=gpu:2`, your total number of cores per node (meaning: -`ntasks`*`cpus-per-task`) may not exceed 12 (on Alpha Centauri) +`ntasks`*`cpus-per-task`) may not exceed 12 on Alpha Centauri. Note that this also has implications for the use of the `--exclusive` parameter. -Since this sets the number of allocated cores to 48, you also **must** request all eight GPUs -by specifying `--gres=gpu:8`, otherwise your job will not start. +Since this sets the number of allocated cores to the maximum, you also **must** request all GPUs otherwise your job will not start. In the case of `--exclusive`, it won't be denied on submission, because this is evaluated in a later scheduling step. Jobs that directly request too many cores per GPU will be denied with the error message: -- GitLab