Skip to content

Owner Group Usage: ember

The following constraint utilization information can be used to (possibly) minimize the chance of preemption when running guest jobs. Note, however, that the past usage of a group does not indicate their future behavior; preemption is still possible when using the results presented here. Also, the available cores and memory on each node may differ, so check that you are using valid constraints that will allow the job to run. The sinfo aliases si and si2 (documented on the Slurm page) can be used to determine the number of cores and total memory on each node and multiple constraints can be specified by using logical operators. This same technique can be used to specify multiple groups (nodes with some constraint or another). For more information, see the introduction on the index page.

Last Updated: 6/10/21