[slurm-users] Areas for improvement on our site's cluster scheduling

[Bjørn-Helge Mevik]

Jonathon A Anderson <jonathon.anderson at colorado.edu> writes:

> ## Queue stuffing

There is the bf_max_job_user SchedulerParameter, which is sort of the
"poor man's MAXIJOB"; it limits the number of jobs from each user the
backfiller will try to start on each run.  It doesn't do exactly what
you want, but at least the backfiller will not create reservations for
_all_ the queue stuffer's jobs.

Also, there is the sacctmgr setting

MaxJobs=<max jobs>
       Maximum number of jobs each user is allowed to run at one time in this asso-
       ciation.   This  is  overridden  if  set directly on a user.  Default is the
       cluster’s limit.  To clear a previously set value  use  the  modify  command
       with a new value of -1.

Another alternative is to get the user to use array jobs, where (s)he
can specify how many jobs are to be allowed to run at the same time, but
of course this means the user must cooperate. :)

-- 
Regards,
Bjørn-Helge Mevik, dr. scient,
Department for Research Computing, University of Oslo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20180508/06c47534/attachment-0001.sig>