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).
Best, Lyn On 9/4/12, Lennart Karlsson <[email protected]> wrote: > > Hi, > > I noticed something strange this week. When > running "sprio" I get > JOBID PRIORITY AGE FAIRSHARE JOBSIZE QOS > 2176240 120160 20160 100000 0 0 > 2176574 120160 20160 100000 0 0 > 2176609 100000 0 100000 0 0 > 2177022 120160 20160 100000 0 0 > > All jobs were submitted very recently, just some minute ago. > > But some jobs get an age value of zero and some get the > maximum (in this system) age value of 20160. > > In slurm.conf, I have defined: > PriorityMaxAge=14-0 > PriorityWeightAge=20160 > > The plan behind this configuration is to get approximately > one priority point for each minute that the job has been > waiting, up to a maximum of 20160. Now this goes very wrong. > > Does anyone have any idea regarding what is in error here? > > Cheers, > -- Lennart Karlsson > UPPMAX, Uppsala University, Sweden > http://www.uppmax.uu.se >
