...
Node priority: With Torque/Moab we can control the order in which the scheduler picks nodes. This allows us to run jobs on the faster nodes by default.
- Slurm
- I don't know how to set priorities in Slurm like we do in Torque where batch jobs get the faster nodes and interactive jobs get the slower nodes. There is a Weight feature to a NodeName where the lowest weight will be chosen first but that will affect batch and interactive partitions equally. I need another axis.
- The order of the nodes in PartitionName is not important. But you can set a Weight to a NodeName. Nodes with the lowest weight will be chosen first. Default is 1 and must be an integer.
NodeName=testpost001 Weight=100 CPUs=16 Boards=1 SocketsPerBoardSockets=2 CoresPerSocket=8 ThreadsPerCore=1 RealMemory=193370 Weight=2
NodeName=testpost002 Weight=100 CPUs=16 Boards=1 SocketsPerBoard=Sockets=2 CoresPerSocket=8 ThreadsPerCore=1 RealMemory=193370 Weight=1
- HTCondor
- There isn't a simple list like pbsnodes in Torque but there is NEGOTIATOR_PRE_JOB_RANK which can be used to weight nodes by cpu, memory, etc.
- OpenPBS
- Doesn't have a nodes file so I don't know what drives the order of the nodes chosen for jobs.
- Slurm
...