Janne, In re-reading the section from your message below, I wondered whether you had tried setting in sacctmgr the "FairShare=parent" setting for in your user associations. It might have a beneficial effect on the problem you describe.
This setting is described in the multifactor web page... FairShare=parent It is possible to disable the fairshare at certain levels of the fair share hierarchy by using the FairShare=parent option of sacctmgr. For users and accounts with FairShare=parent the normalized shares and effective usage values from the parent in the hierarchy will be used when calculating fairshare priories. If all users in an account is configured with FairShare=parent the result is that all the jobs drawing from that account will get the same fairshare priority, based on the accounts total usage. No additional fairness is added based on users individual usage. > -----Original Message----- > From: Janne Blomqvist [mailto:[email protected]] > Sent: Thursday, August 23, 2012 12:05 AM > To: slurm-dev > Subject: [slurm-dev] Making hierarchical fair share hierarchical > > [...] > The problem we're seeing is that the current hierarchical fair-share > algorithm does not manage to do this in our case. Our issues seems to be > partly due to the departments having somewhat different usage patterns. > The departments have a roughly equal amount of users, but for two of the > departments (lets call them A and B) most of the users use the cluster > very little, but with a few heavy users. The third department, OTOH, has > a much larger number of active users. The end result of this is that the > heavy users of the A and B departments have very low fair-share > priorities, and department C manages to use most of the resources since > their users have higher fair-share priorities, despite the usage at the > department level being far away from the fair-share target. [...] > Janne Blomqvist
