[slurm-users] How to weight nodes properly based on RAM to prevent small instances clogging big instances with backfilling
7 views
Skip to first unread message
Xaver Stiensmeier via slurm-users
unread,
May 28, 2026, 10:40:53 AMMay 28
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to slurm...@lists.schedmd.com
Dearl Slurm User List,
I am currently reviewing a slurm.conf where the developer set Weight
manually to attribute a greater weight to machines that have more RAM to
force smaller jobs on smaller instances. However, I feel like there is
something already in place or better than manually setting the weights,
but I couldn't find it.
If I understand correctly Slurm does not schedule jobs to the smallest
possible node on default. So small jobs can be scheduled to large
instances and a big job might have to wait indefinitely when using
backfilling.
I thought that Slurm does have mechanisms to prevent this but was unable
to find it again in the documentation.
Is there really no automatism at place or am I overlooking something?
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Xaver Stiensmeier, slurm...@lists.schedmd.com
IIRC the thing you can't find is simply the order in which the nodes are listed in the partition definition (or alphanumerical order if they are added en masse with square brackets)