Differences

This shows you the differences between two versions of the page.

--- scheduling [2014/04/24 11:29]
root
+++ scheduling [2020/03/11 17:13] (current)
root
@@ Line 1: / Line 1: @@
 ====== Scheduling ======
-The cluster is running SLURM's default scheduler which is very (maybe too) simple.
+The cluster is running SLURM's scheduler with:
-  * first-in first-out queue.
+  * "Fair share" job priorities.
   * Simple round-robin node selection.
-The scheduler does not check which nodes are busy and try to avoid them.
+The "Fair Share" algorithm assigns a priority to submitted jobs which is inversely dependent on the amount of cluster CPU time consumed by the user submitting the jobs in recent days. These priorities apply only to jobs waiting in the queue, they do not affect jobs which are already running.
-This has an advantage in that it tends to leave some nodes empty for people who want a whole node.
-You can use the **-w** option to select a specific node. Actually it asks for "at least" the nodes in the node list you specify. So a command like:
-<code>
-sbatch -n 20 -w node2
-</code>
-Would get you some cores on node2 and some on another node (since there is only 16 cores on node2). If there were no cores free on node2 the job would be queued until some became available.
-You can use the **-x** option to avoid specified nodes.
-You can use **-c 16** to request all cores on a (standard) node.
-You can use the **--exclusive** option to as for exclusive access to all the nodes your job is allocated. This is especially useful if you have a program which attempts to use all the cores it finds.
+The scheduler does not check which nodes are busy and try to avoid them. This has an advantage in that it tends to leave some nodes empty for people who need a whole node.

BRC Cluster Workshop

User Tools

Site Tools

Differences

Page Tools