On Tue, 24 May 2011, Dave Love wrote:

..._RESERVED_USAGE are at least badly documented.  When I came across
them I interpreted `reserved' to mean resource reservation, i.e. the
overhead from doing that.  I'll fix the doc; does anyone have a good
suggestion for a better description?  I'm inclined to say `available
resources' and explain further.  I haven't got round to checking, but I
assume what's used for cpu is running time multiplied by slot count;
anyone know what's used for io, which is specifically mentioned?

I took a look at this when I was fiddling around with usage_weight_list setting. With ..._RESERVED_USAGE=true, the values are equal to:

  cpu = slots * seconds
  mem = slots * seconds * gigabytes-per-slot
  io  = (don't know - haven't looked yet)

I've not looked at the code yet, but I did test GE 6.2u5 to check that these are indeed the values that find their way into the sharetree (if using SHARETREE_RESERVED_USAGE) or the accounting file (if using ACCT_RESERVED_USAGE).

It was an interesting doing this - it also made me appreciate that the PE configuration can cause 1 to be added to the slots count in the above calculations (I think it was some combination of control_slaves and job_is_first_task).


Also, I wonder why SHARETREE_RESERVED_USAGE is deprecated, as it seems
more useful default.
...

I couldn't agree more.

Personally, the only reason I'd use ACCT_RESERVED_USAGE would be to verify the numbers being fed into the sharetree.

e.g. after fiddling around with usage_weight_list and I wanted to check
the result on particular types of job (it's easier than subtracting the history from the "usage" values stored in the sharetree)

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

Reply via email to