[slurm-users] Priority setup for some typical use cases?

René Neumaier r.neumaier at lrz.uni-muenchen.de
Sun Sep 15 09:41:38 UTC 2019


Hello Vang Le-Quy,

On 14.09.19 17:55, Vang Le-Quy wrote:
> Our system does not allow much testing at the moment so I want to make use of community knowledge. The multifactor plugin has many handles to tweak. That makes it powerful and daunting at the same time. Basically how do you setup for various user groups based on urgency, resource usage, and resource guaranty?

With the multifactor plugin and QOS? :-)
It's not so complicated. I would recommend you create 1-2 virtual
machines and play a bit with the appropriate options (see below).


> How do I define a ‘developers’ partition for development that allows user to run temporary debug session with maximum walltime of 8:00:00 hours (MaxTime=8:00:00). Furthermore, jobs in this partition have highest priority, and are preferably started right away? Do I need also setup a ‘debug’ QOS as well? Last but not least, if the time is up for a job in this partition, can I set the job to be in suspended state.

As far as I know slurm partitions are mainly used to group the
same/similar hardware.

What can fit your needs is:
https://slurm.schedmd.com/qos.html
https://slurm.schedmd.com/preempt.html

Just deactivate the other factors for the moment:
PriorityType=priority/multifactor
PriorityWeightAge=0
PriorityWeightFairshare=0
PriorityWeightJobSize=0
PriorityWeightPartition=0
PriorityWeightQOS=10000

Do not shy away from the slurmdb setup (which is mandatory for this
solution). It is worth the trouble.
In the future you can also create extensive statistics.
For example, which users regularly occupy CPUs/RAMs but do not use them
to full capacity (which means waste of CPU time).


Best,
René

-- 
_____________________________
René Neumaier
Systemadministration

LMU München
Department für Geo und
Umweltwissenschaften,
Paläontologie & Geobiologie

Richard-Wagner-Str. 10
D-80333 München
Tel.: +4989-2180-6625
Fax.: +4989-2180-6601
rene.neumaier at lmu.de
r.neumaier at lrz.uni-muenchen.de

GPG-Fingerprint:
EC0E B6F6 B3FF 6324 B0C8 9452 EF6B 4E3C 2E59 F5AA

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20190915/233b0c66/attachment.sig>


More information about the slurm-users mailing list