I was wondering if it is possible in SLURM to have the scheduler charge for both CPU time and memory usage? After in a setting where you don't have exclusive access to each node you can end up in a situation where a node may only be using one core but all the memory. In SLURM if you are just doing CPU charging you only get hit for the 1 core you are using, not for the additional other cores (lets say for the sake of argument 64 total cores per node) that are idling because no other job can run. That seems unfair.

Thoughts? If this doesn't exist it may be a good thing to add into the next version of SLURM as it would be handy in our environment.

-Paul Edmon-

Reply via email to