Could you just create a dedicated queue for those jobs, and then configure its priority and max simultaneous settings? Then all they would have to do is ensure they submit those jobs to that queue.
On Jun 19, 2013, at 8:36 AM, Paul Edmon <ped...@cfa.harvard.edu> wrote: > > I have a group here that wants to submit a ton of jobs to the queue, but > want to restrict how many they have running at any given time so that > they don't torch their fileserver. They were using bgmod -L in LSF to > do this, but they were wondering if there was a similar way in SLURM to > do so. I know you can do this via the accounting interface but it would > be good if I didn't have to apply it as a blanket to all their jobs and > if they could manage it themselves. > > If nothing exists in SLURM to do this that's fine. One can always > engineer around it. I figured I would ping the dev list first before > putting a nail in it. From my look at the documentation I don't see > anyway to do this other than what I stated above. > > -Paul Edmon-
