I have a user asking about a SLURM config setting that would allow a job to not 
tie up a node's unused resources, thereby allowing another job to run 
concurrently.

User:
On our cluster, our Fluent GPU jobs each use only 1 of the 2 GPUs on 
GPUServer[1,2]. Currently the node is fully allocated to whichever job lands on 
it first, leaving the second GPU, 38 CPU cores, and 270+ GB of RAM idle.

Has anyone dealt with this? What options would facilitate this? Are there any 
gotchas or pitfalls?

-- 
slurm-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to