On 09/04/2012 11:38 PM, Lyn Gerner wrote:
>
> Guess it doesn't matter, does it? :) PriorityWeightAge=1
>
> On 9/4/12, Lyn Gerner<[email protected]> wrote:
>> Ouch -- reverse that: (14 days * 24hrs * 60mins) / 20160
>>
>> On 9/4/12, Lyn Gerner<[email protected]> wrote:
>>> Hi Lennart,
>>>
>>> I believe the value being reported in the AGE column of the sprio
>>> output is the product of the job's current age * PriorityWeightAge. I
>>> believe for your purposes, that you want to pick a much lower number
>>> for your PriorityWeightAge value, such as 20160 / (14 days * 24hrs *
>>> 60mins).
Hi Lyn,
Confusing, is it not? :-)
A few minutes ago, I sent some debugging output to the mailing list.
In an example,
[2012-09-05T00:07:31] Weighted Age priority is 0.004721 * 20160 = 95.17
for a job that had waited since 2012-09-04T22:32:08, so normally
it seems to work as intended, i.e. approximately one priority point
for each minute in queue.
I do not know if SLURM or my configuration or some trick with
time values (yes, I use ntp daemons) or something else creates
this problem that appears sometimes, but not always.
Thanks,
-- Lennart Karlsson
UPPMAX, Uppsala University, Sweden
http://www.uppmax.uu.se
