Quoting "Skouson, Gary B" <[email protected]>:
I'm looking for a way to prioritize jobs so that users with jobs
running get lower priority than those without jobs running. I'd
like the priority to be independent of the job size or past usage.
For example, one user may have three single-node jobs and another
user has a single 300-node job running. I'd like the user with the
single job running to have their pending jobs get priority, until
both users have the same number running. Similarly, a user with
several 100-node jobs would get lower priority than a user with
nothing running that submits a single-node job.
From what I can tell, the current priority policies have cpu-hours
as part of the priority equation, but not "number of currently
running jobs". Any ideas, or pointers to something I've missed? Any
other way to do this?
-----
Gary Skouson
Your closest option with Slurm today is to prioritize jobs based upon
fair-share usage (historic) usage with everyone getting the same share
of resources, but configuring a small half-life decay on usage
("PriorityDecayHalfLife=1"). For more information, see:
http://slurm.schedmd.com/priority_multifactor.html
--
Morris "Moe" Jette
CTO, SchedMD LLC
Commercial Slurm Development and Support
