Hi,
Please review the settings in slurm.conf for oversubscribe for cpu cores
and setting jobs to use oversubscribe in sbatch. I don't know if it is
still true, but delete the boards=1 from node definition. It used to mess
up the math.
Doug
On Wed, Mar 27, 2024, 7:09 AM Guillaume COCHARD via
We do it by assigning fairshare just to the account.
sacctmgr -i add account $acct Description="$descr" \
Organization="$org" fairshare=200 GrpJobsAccrue=8
sacctmgr -i add user "$u" DefaultAccount=$acct fairshare=parent
Add the same user to other accounts with
sacctmgr -i add
Hello,
We have upgraded our cluster to Slurm 23.11.1 then, a few weeks later, to
23.11.4. Since then, Slurm doesn't detect hyperthreaded CPUs. We have
downgraded our test cluster, the issue is not present with Slurm 22.05 (we had
skipped Slurm 23.02).
For example, we are working with this
For this use case you probably want to go with Classic Fairshare
(https://slurm.schedmd.com/classic_fair_share.html) rather than
FairTree. Classic Fairshare behaves in a way similar to what you
describe. You can set up different bins for fairshare and then the user
can pull from them. So that
Hi,
I’m trying to set up multifactor priority on our cluster and am having some
trouble getting it to behave the way I’d like. My main issues seem to revolve
around FairShare.
We have multiple projects on our cluster and multiple users in those projects
(and some users are in multiple
