Thanks Reuti, you're awesome!
I thought the halftime just dictated the length of time usage took
before it was half its original value. It seems to be that that is not
the same as how long the scheduler keeps usage information for jobs.
Although, at some point, say 4-5 halflife cycles the decayed usage is
very small and doesn't have much of an impact.
--
Brian McNally
On 05/08/2013 01:46 PM, Reuti wrote:
Hi,
Am 08.05.2013 um 22:30 schrieb Brian McNally:
qacct reports usage from a file, but GE has its own internal database for
tracking jobs and usage.
You mean for the share tree policy? Yes.
Is this correct? If so, what controls the length of time GE keeps job data for?
The "halftime" setting in the scheduler configuration (`man sched_conf`).
It seems that using qacct to display overall usage per user (-o), for example,
might be a little misleading if the actual accounting information is stored
internally. Users might draw conclusions about their usage and how that'll
impact their job priorities based on potentially incorrect data.
Unfortunately this is correct. You can even remove the accouting file or rotate it which
might lead to even different output. It would be hard to mimic the internal computation.
Maybe setting "report_pjob_tickets" to true could give them a hint at which
position their jobs are in the pending list (usually it's switched off for performance
reasons).
-- Reuti
Thanks,
--
Brian McNally
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
