Mike, it feels like there may be other PriorityWeight terms that are non-zero in your config. QoS or partition-related, perhaps?
Regards, Lyn On Mon, Jun 13, 2022 at 5:55 AM <z1...@arcor.de> wrote: > > Dear all, > > I noticed different priority calculations by running a pipe, the > settings are for example: > > PriorityType=priority/multifactor > PriorityWeightJobSize=100000 > AccountingStorageTRES=cpu,mem,gres/gpu > PriorityWeightTRES=cpu=1000,mem=2000,gres/gpu=3000 > > No age factor or something else from the plugin. > > > The calculated priority for memory and cpus: > mem 1024, cpus 1, priority 25932 > mem 123904, cpus 14, priority 38499 > mem 251904, cpus 28, priority 20652 > mem 251904, cpus 28, priority 14739 > > > gres or gpu was not available on the jobs/instances. > > > Someone know why the priority changed with the same cpu and mem input? > > The priority with these settings should be descending, highest priority > for mem 251904 with cpus 28 and lowest priority for mem 1024 with cpus 1. > > > Many thanks, > > Mike > >
