[slurm-users] Multifactor priority configuration

[Hadrian Djohari]

Hi Killian,

We choose to penalize the users a little only for their previous busy jobs,
so we choose short turnarounds.
PriorityDecayHalfLife=1-0
PriorityMaxAge=4-0

The busier the cluster, the longer should the parameters be, so the user
previous jobs will restrict the "future" ones more.
These should be adjusted based on the actual usage and impact to the users.

Best,
Hadrian

On Wed, Jan 22, 2020 at 4:22 AM Killian Murphy <killian.murphy at york.ac.uk>
wrote:

> Hi all.
>
> I’m interested to learn what people are using for the following
> configuration items:
>
>    - PriorityDecayHalfLife
>    - PriorityMaxAge
>
> and why they have chosen to set these as they have. I believe we haven’t
> got these set quite right on our cluster (3-0 for both items), and some
> understanding of what other people are doing with these settings might help
> us to get this right!
>
> For context, ours is a tier 3 cluster servicing mixed workloads.
>
> Thanks.
>
> Killian
> --
> Killian Murphy
> Research and High Performance Computing Team Leader
> Research Software Engineer
>
> Information Services & Wolfson Atmospheric Chemistry Laboratories
> University of York
> Heslington
> York
> YO10 5DD
> +44 (0)1904 32 4753
>
> e-mail disclaimer: http://www.york.ac.uk/docs/disclaimer/email.htm
>


-- 
Hadrian Djohari
Manager of Research Computing Services, [U]Tech
Case Western Reserve University
(W): 216-368-0395
(M): 216-798-7490
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20200122/1b6a758e/attachment.htm>