[gridengine users] Making the fair-share policy/scheduler algorithm "more fair"
jake.carroll at uq.edu.au
Wed May 1 00:50:05 UTC 2013
Thanks for the response. This is opening up a bunch of cool ideas for us.
We're trying to get our heads around how the scaling factor stuff actually
For example, if a host policy says scale factor for mem = 1.0, but we
could perhaps set it to 0.50, what does that actually *mean*? How does it
change the "scale" factor and what impact does it have on the way the
scheduler works to utilise memory on that that node? Trying to get a
better handle on the semantics of this thing.
For example, we have "small" node and a "large" node in the same queue,
root at cluster ~]# qconf -se compute-0-0
[root at cluster ~]# qconf -se compute-1-0
So - how does the scale factor etc actually impact the schedulers use of
On 30/04/13 9:12 PM, "Mark Dixon" <m.c.dixon at leeds.ac.uk> wrote:
>On Fri, 26 Apr 2013, Jake Carroll wrote:
>> Anyway. What I would really like to know is, if it's possible to weight
>> and "fair-share" based on something other than slots utilisation. Can a
>> user weight on memory utilisation for example? What I'd really like to
>> be able to do is prioritise and weight users down who slam the HPC
>> environment with big high memory jobs, such that they are
>> once their jobs have run, so it gives other users a fair swing at the
>> lovely DIMM modules too.
>We use the share tree here, rather than the functional policy, so this
>might not be applicable.
>By default, the "usage" of a job is wholly based on slots*seconds. You
>introduce memory (in gigabytes*seconds) by editing the
>parameter in "qconf -ssconf". We certainly did :)
>See the sched_conf man page for more details.
>If you don't have the same amount of RAM everywhere, you might also want
>to play with "usage_scaling" parameters in the execd host definitions.
>Good luck :)
>Mark Dixon Email : m.c.dixon at leeds.ac.uk
>HPC/Grid Systems Support Tel (int): 35429
>Information Systems Services Tel (ext): +44(0)113 343 5429
>University of Leeds, LS2 9JT, UK
More information about the users