techstaff:slurm
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
techstaff:slurm [2020/03/25 14:17] – [Announcements] kauffman | techstaff:slurm [2020/10/07 13:06] – kauffman | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Announcements ====== | ||
- | * **2020-03-25**: | ||
- | |||
- | |||
====== Peanut Job Submission Cluster ====== | ====== Peanut Job Submission Cluster ====== | ||
Think of these machines as a dumping ground for discrete computing tasks that might be rude or disruptive to execute on the main (shared) shell servers (i.e., linux1, linux2, linux3). | Think of these machines as a dumping ground for discrete computing tasks that might be rude or disruptive to execute on the main (shared) shell servers (i.e., linux1, linux2, linux3). | ||
- | For job submission we will be using a piece of software called [[http:// | + | For job submission we will be using a piece of software called [[http:// |
"Slurm is an open-source workload manager designed for Linux clusters of all sizes. It provides three key functions. First it allocates exclusive and/or non-exclusive access to resources (computer nodes) to users for some duration of time so they can perform work. Second, it provides a framework for starting, executing, and monitoring work (typically a parallel job) on a set of allocated nodes. Finally, it arbitrates contention for resources by managing a queue of pending work." | "Slurm is an open-source workload manager designed for Linux clusters of all sizes. It provides three key functions. First it allocates exclusive and/or non-exclusive access to resources (computer nodes) to users for some duration of time so they can perform work. Second, it provides a framework for starting, executing, and monitoring work (typically a parallel job) on a set of allocated nodes. Finally, it arbitrates contention for resources by managing a queue of pending work." | ||
- | SLURM is similar to most other queue systems in that you write a batch script, then submit it to the queue manager. The queue manager schedules your job to run on the queue (or partition in SLURM parlance) that you designate. Below is an outline of how to submit jobs to SLURM, how SLURM decides when to schedule your job, and how to monitor progress. | + | Slurm is similar to most other queue systems in that you write a batch script, then submit it to the queue manager. The queue manager schedules your job to run on the queue (or partition in Slurm parlance) that you designate. Below is an outline of how to submit jobs to Slurm, how Slurm decides when to schedule your job, and how to monitor progress. |
===== Where to begin ===== | ===== Where to begin ===== | ||
- | SLURM is a set of command line utilities that can be accessed via the command line from **most** any computer science system you can login to. Using our main shell servers (linux.cs.uchicago.edu) is expected to be our most common use case, so you should start there. | + | Slurm is a set of command line utilities that can be accessed via the command line from **most** any computer science system you can login to. Using our main shell servers (linux.cs.uchicago.edu) is expected to be our most common use case, so you should start there. |
ssh user@linux.cs.uchicago.edu | ssh user@linux.cs.uchicago.edu | ||
Line 26: | Line 22: | ||
===== Documentation ===== | ===== Documentation ===== | ||
- | The [[http:// | + | The [[http:// |
- | A great way to get details on SLURM commands are the manuals that are already on the cluster. For example, if you type the following command: | + | A great way to get details on Slurm commands are the manuals that are already on the cluster. For example, if you type the following command: |
man sbatch | man sbatch | ||
you will get the manual page for the '' | you will get the manual page for the '' | ||
===== Resources ===== | ===== Resources ===== | ||
- | * [[https:// | + | * [[https:// |
* [[http:// | * [[http:// | ||
- | * [[http:// | + | * [[http:// |
* [[http:// | * [[http:// | ||
* [[https:// | * [[https:// | ||
Line 139: | Line 135: | ||
===== Command Summary ===== | ===== Command Summary ===== | ||
[[http:// | [[http:// | ||
- | | ^ SLURM ^ Example ^ | + | | ^ Slurm ^ Example ^ |
^ Submit a batch serial job | sbatch | sbatch runscript.sh | | ^ Submit a batch serial job | sbatch | sbatch runscript.sh | | ||
^ Run a script interactively | srun | srun --pty -p interact -t 10 --mem 1000 \\ /bin/bash \\ / | ^ Run a script interactively | srun | srun --pty -p interact -t 10 --mem 1000 \\ /bin/bash \\ / | ||
Line 223: | Line 219: | ||
==== sinfo ==== | ==== sinfo ==== | ||
- | View information about SLURM nodes and partitions. | + | View information about Slurm nodes and partitions. |
The following code block shows the what happens when you run the '' | The following code block shows the what happens when you run the '' | ||
Line 240: | Line 236: | ||
====== Monitoring Jobs ====== | ====== Monitoring Jobs ====== | ||
- | '' | + | '' |
Running '' | Running '' | ||
Line 263: | Line 259: | ||
====== Job Scheduling ====== | ====== Job Scheduling ====== | ||
- | We use a [[http:// | + | We use a [[http:// |
- | We also have backfill turned on. This allows for jobs which are smaller to sneak in while a larger higher priority job is waiting for nodes to free up. If your job can run in the amount of time it takes for the other job to get all the nodes it needs, | + | We also have backfill turned on. This allows for jobs which are smaller to sneak in while a larger higher priority job is waiting for nodes to free up. If your job can run in the amount of time it takes for the other job to get all the nodes it needs, |
Line 383: | Line 379: | ||
==== CUDA_VISIBLE_DEVICES ==== | ==== CUDA_VISIBLE_DEVICES ==== | ||
- | Do not set this variable. It will be set for you by SLURM. | + | Do not set this variable. It will be set for you by Slurm. |
The variable name is actually misleading; since it does NOT mean the amount of devices, but rather the physical device number assigned by the kernel (e.g. / | The variable name is actually misleading; since it does NOT mean the amount of devices, but rather the physical device number assigned by the kernel (e.g. / |
/var/lib/dokuwiki/data/pages/techstaff/slurm.txt · Last modified: 2021/01/06 16:13 by kauffman