Hi,if you want to affect priority, you can create additional partitions that contain nodes of a certain type, like bigmem, ibnet, etc. and set a priority boost of your choosing. Jobs that require certain features or exceed predefined thresholds can be then filtered and assigned to the appropriate p
Chris,
Thanks for the response. I am already doing that with weights for the
nodes, but I was hoping to go one step further. Personally, I think
using weights like this should be an acceptable approach, but during a
user discussion, users, wanted the large memory jobs to "go to the head
of th
Hi;
We use node weight parameter to do that. When you set High mem nodes
with high weight, and low mem nodes with low weight; Slurm will select
lowest weight nodes which have enough mem job requested. So, if there
are free low mem nodes, high mem nodes will stay free. At our cluster,
low mem
Prentice,
I don't have a good answer to your original question, but I'll note I have a
similar concern and solved it a different way. What we did was use lower
weights in the node definitions for the "smaller" (less feature-rich) nodes,
and extra high weights for nodes with unique features (l
Ryan,
I certainly understand your point of view, but yes, this is definitely
what I want. We only have a few large memory nodes, so we want jobs that
request a lot of memory to have higher priority so they get assigned to
those large memory nodes ahead of lower-memory jobs which could run
any
