On Wed, 23 Mar 2011, Reuti wrote:
...
1) Sometime between 6.0 and 6.2, ACCT_RESERVED_USAGE also started
making maxvmem show the reserved usage in the accounting file.
True - was this behavior discussed on any list before, whether it's a
feature or a bug?
I've not seen the behaviour change mentioned on the list, but I'm not as
extensive a list reader/contributor as you are. I'm only posting more now
because I've not written a new mail filter since the old list got closed
down ;)
I used Dave's copy of the CVS to track down the change. As I recall, I
think it was collateral damage from fixing a different bug.
When "cpu" and "mem" is already the reserved integral
value, you can compute this "maxvmem" easily affterwards. There it no
need to set it IMO.
They completely different things, aren't they? Isn't maxvmem the peak vmem
used during the job, whereas mem ought to be the time integral?
Besides, even if you can calculate it from the other fields, having
maxvmem is so much easier to read for the users e.g. to see how much vmem
they used, so they know what to ask for in subsequent similar jobs.
Back in 6.0-land, it also was the most reliable method I could find to see
if your job failed due to exceeding any requested h_vmem.
2) It's interesting to have the actual cpu time in the accounting file,
so that you can see if cpu time / run time ~= 1.0
Yes, as long as the jobs are not reprioritized with different nice
values and/or the exechosts are oversubscribed, i.e. you have
slots=cores.
You would charge for the run time then (in case you do it)?
We charge for elapsed time, which we get from ru_wallclock.
Best wishes,
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
