On Thu, 24 May 2012, [email protected] wrote:
...
If possible, it would be extremely helpful to express memory limits as a
percentage of available resources, rather than just as a fixed quantity.
Yes, I do the trick of extracting the swap and RAM sizes for each server
and putting those values into a consumable. This is not transparent to
maintain as servers are updated. From and end-user point of view I'd
much rather do somthing like:
-l vmem=60G -l swap=75%
to express that my job may use up to 60GB of total memory (in any
combination of RAM + swap that the OS needs to allocate), but would not
be permitted to use over 75% of swap.
In other words, allow users a lot of latitude in running jobs (even accepting
the slowdown of using swap, if needed), but prevent memory starvation that
causes the OOM-killer to activate.
...
Yikes, that sounds hard.
I've not looked at the qmaster code that would need to deal with this, but
you want to change an assumption that, if I had written the code making
it, would need major surgery to do.
In some simple situations you can of course cheat - for example:
* If all your hosts has the same amount of swap, you can just translate
the percentage to an absolute value using the JSV feature.
* If you never want to use an absolute value, you can put in a consumable
value of 100 and hack the execd code to interpret the number however you
like.
Mark
--
-----------------------------------------------------------------
Mark Dixon Email : [email protected]
HPC/Grid Systems Support Tel (int): 35429
Information Systems Services Tel (ext): +44(0)113 343 5429
University of Leeds, LS2 9JT, UK
-----------------------------------------------------------------
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
