Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revisionBoth sides next revision | ||
technical:slurm:node-memory-sizes [2019-02-18 12:25] – [Nominal node memory size is not an appropriate limit] frey | technical:slurm:node-memory-sizes [2019-02-18 12:32] – [Proposed RealMemory sizes] frey | ||
---|---|---|---|
Line 86: | Line 86: | ||
A workgroup QOS which under v1.1.3 had '' | A workgroup QOS which under v1.1.3 had '' | ||
+ | |||
+ | ==== Requesting specific node types ==== | ||
+ | |||
+ | Our Slurm defines several // | ||
+ | |||
+ | <code bash> | ||
+ | $ scontrol show node r00n00 | ||
+ | NodeName=r00n00 Arch=x86_64 CoresPerSocket=36 | ||
+ | | ||
+ | | ||
+ | | ||
+ | : | ||
+ | </ | ||
+ | |||
+ | It is possible to constrain a job to execute on a node with a specific nominal memory size using these features: | ||
+ | |||
+ | <code bash> | ||
+ | $ sbatch … --constraint=128GB … | ||
+ | $ sbatch … --constraint=256GB … | ||
+ | $ sbatch … --constraint=512GB … | ||
+ | </ | ||
+ | |||
+ | The other features reflect the model processor present in the node. All Gen1 nodes use the Intel '' | ||
===== Implementation ===== | ===== Implementation ===== | ||