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 [2017/11/13 10:02] – kauffman | techstaff:slurm [2018/05/03 09:53] – [Using the GPU] kauffman | ||
---|---|---|---|
Line 11: | Line 11: | ||
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 ===== | ||
Line 17: | Line 19: | ||
ssh user@linux.cs.uchicago.edu | ssh user@linux.cs.uchicago.edu | ||
+ | ===== Mailing List ===== | ||
+ | If you are going to be a user of this cluster please sign up for the mailing list. Downtime and other relevant information will be announced here. | ||
+ | |||
+ | [[ https:// | ||
===== Documentation ===== | ===== Documentation ===== | ||
Line 32: | Line 38: | ||
* [[https:// | * [[https:// | ||
* [[http:// | * [[http:// | ||
+ | |||
+ | |||
===== Infrastructure ===== | ===== Infrastructure ===== | ||
Line 56: | Line 64: | ||
Request interactive shell | Request interactive shell | ||
< | < | ||
+ | |||
+ | Create a directory on the scratch partition if you don't already have one: | ||
+ | < | ||
Change into my scratch directory: | Change into my scratch directory: | ||
- | < | + | < |
Get the files I need: | Get the files I need: | ||
< | < | ||
- | user@research2:/ | + | user@slurm1:/ |
foo | foo | ||
</ | </ | ||
Check that the file now exists: | Check that the file now exists: | ||
< | < | ||
- | user@research2:/ | + | user@slurm1:/ |
-rw------- 1 user user 105121 Dec 29 2015 foo | -rw------- 1 user user 105121 Dec 29 2015 foo | ||
</ | </ | ||
Line 75: | Line 86: | ||
== Performance is slow == | == Performance is slow == | ||
This is expected. The maximum speed this server will ever be able to achieve is 1Gb/s because of its single 1G ethernet uplink. If this cluster gains in popularity we plan on upgrading the network and storage server. | This is expected. The maximum speed this server will ever be able to achieve is 1Gb/s because of its single 1G ethernet uplink. If this cluster gains in popularity we plan on upgrading the network and storage server. | ||
+ | |||
==== Utilization Dashboard ==== | ==== Utilization Dashboard ==== | ||
Sometimes it is useful to see how much of the cluster is utilized. You can do that via the following URL: http:// | Sometimes it is useful to see how much of the cluster is utilized. You can do that via the following URL: http:// | ||
Line 233: | Line 245: | ||
====== Using the GPU ====== | ====== Using the GPU ====== | ||
+ | |||
+ | ===== GRES Multiple GPU's on one system ===== | ||
+ | Jobs will not be allocated any generic resources unless specifically requested at job submit time using the --gres option supported by the salloc, sbatch and srun commands. The option requires an argument specifying which generic resources are required and how many resources. The resource specification is of the form name[: | ||
+ | sbatch --gres=gpu: | ||
+ | |||
+ | Jobs will be allocated specific generic resources as needed to satisfy the request. If the job is suspended, those resources do not become available for use by other jobs. | ||
+ | |||
+ | Job steps can be allocated generic resources from those allocated to the job using the --gres option with the srun command as described above. By default, a job step will be allocated all of the generic resources allocated to the job. If desired, the job step may explicitly specify a different generic resource count than the job. This design choice was based upon a scenario where each job executes many job steps. If job steps were granted access to all generic resources by default, some job steps would need to explicitly specify zero generic resource counts, which we considered more confusing. The job step can be allocated specific generic resources and those resources will not be available to other job steps. A simple example is shown below. | ||
+ | |||
+ | |||
===== Paths ===== | ===== Paths ===== | ||
You will need to add the following to your $PATH and $LD_LIBRARY_PATH. | You will need to add the following to your $PATH and $LD_LIBRARY_PATH. |
/var/lib/dokuwiki/data/pages/techstaff/slurm.txt · Last modified: 2021/01/06 16:13 by kauffman