Am 31.10.2016 um 00:23 schrieb Benjamin Redling: > Are you aware that as long as SchedulerType
Sorry, typo. I meant *SelectType* (The rest I wrote next is just unfiltered noise from my brain while skimming the conf:) >is not set to anything explicitly, select/linear is the default? > Am 30. Oktober 2016 19:00:28 MEZ, schrieb Vlad Firoiu <vlad...@gmail.com>: [...] > ## SelectType=select/linear This seems bad for good utilization. > PriorityType=priority/multifactor > PriorityDecayHalfLife=7-0 > PriorityUsageResetPeriod=MONTHLY I'm undecided about that... > # [...] > PriorityWeightQOS = 100000 > PriorityWeightFairShare = 1000 Clearly dominant QOS/Fairshare: I hope accounting is setup right -- in the "portion" of your slurm.conf you didn't provide? > PriorityWeightAge = 10 Does this even matter compared to QOS and Fairshare? > PriorityWeightJobSize = 1 Reasons for not using PriorityFavorSmall (with or without SMALL_RELATIVE_TO_TIME) and considering the job size? I think that would improve utilization in combination with a SelectType that takes CR into account. The 10min job you mentioned would not starve behind the big ones. > PriorityWeightPartition = 1 > PriorityMaxAge=1-0 This way the age_factor maxes out after one day -- comparatively fast to the default of a week. But age doesn't really matter compared to QOS and Fairshare... what's the idea behind that? > The particular job in question has 0 priority. My fault: to ask for "sprio -w" with the individual weights in the first place would have been nice. Regards, Benjamin -- FSU Jena | JULIELab.de/Staff/Benjamin+Redling.html vox: +49 3641 9 44323 | fax: +49 3641 9 44321
