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/08/21 15:55] – [Notice] kauffman | techstaff:slurm [2018/02/22 17:21] – kauffman | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Notice ===== | + | ===== Notice ===== |
- | The SLURM cluster will become unavailable starting | + | **2017-08-31**: Configuration change to allow allocation |
====== Peanut Job Submission Cluster ====== | ====== Peanut Job Submission Cluster ====== | ||
Line 12: | 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 18: | 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 data will be announced here. | ||
+ | |||
+ | [[ https:// | ||
===== Documentation ===== | ===== Documentation ===== | ||
Line 32: | Line 37: | ||
* [[http:// | * [[http:// | ||
* [[https:// | * [[https:// | ||
+ | * [[http:// | ||
Line 41: | Line 47: | ||
* 64gb RAM | * 64gb RAM | ||
* 2x 500GB SATA 7200RPM in RAID1 | * 2x 500GB SATA 7200RPM in RAID1 | ||
- | |||
- | To better manage the cluster we have virtualized the job submission nodes and give them all resources of the hardware. So, the actual resources you can consume on any one node is: | ||
- | * 14 Cores, 14 threads | ||
- | * 62GB RAM | ||
==== Storage ==== | ==== Storage ==== | ||
Line 81: | Line 83: | ||
== 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 113: | Line 116: | ||
===== Usage ===== | ===== Usage ===== | ||
Below are some common examples. You should consult the [[http:// | Below are some common examples. You should consult the [[http:// | ||
+ | |||
+ | === Default Quotas === | ||
+ | By default we set a job to be run on one CPU and allocate 100MB of RAM. If you require more than that you should specify what you need. Using the following options will do: '' | ||
=== Exclusive access to a node === | === Exclusive access to a node === | ||
Line 122: | Line 128: | ||
=== Sample script === | === Sample script === | ||
Make sure you create a directory in which to deposit the '' | Make sure you create a directory in which to deposit the '' | ||
- | mkdir -p $HOME/ | + | mkdir -p $HOME/ |
< | < | ||
Line 129: | Line 135: | ||
#SBATCH --mail-user=cnetid@cs.uchicago.edu | #SBATCH --mail-user=cnetid@cs.uchicago.edu | ||
#SBATCH --mail-type=ALL | #SBATCH --mail-type=ALL | ||
- | #SBATCH --output=/ | + | #SBATCH --output=/ |
- | #SBATCH --error=/ | + | #SBATCH --error=/ |
#SBATCH --workdir=/ | #SBATCH --workdir=/ | ||
#SBATCH --partition=debug | #SBATCH --partition=debug | ||
Line 136: | Line 142: | ||
#SBATCH --nodes=1 | #SBATCH --nodes=1 | ||
#SBATCH --ntasks=1 | #SBATCH --ntasks=1 | ||
+ | #SBATCH --mem-per-cpu=500 | ||
#SBATCH --time=15: | #SBATCH --time=15: | ||
Line 189: | Line 196: | ||
user@host: | user@host: | ||
PARTITION AVAIL TIMELIMIT | PARTITION AVAIL TIMELIMIT | ||
- | debug* | + | debug* |
- | general | + | general |
+ | pascal | ||
+ | tesla up 3-00: | ||
</ | </ | ||
Line 216: | Line 225: | ||
srun -p general --pty --cpus-per-task 1 --mem 500 -t 0-06:00 /bin/bash | srun -p general --pty --cpus-per-task 1 --mem 500 -t 0-06:00 /bin/bash | ||
will start a command line shell ('' | will start a command line shell ('' | ||
- | ====== Job Scheduling ====== | ||
+ | |||
+ | ====== Job Scheduling ====== | ||
We use a [[http:// | We use a [[http:// | ||
/var/lib/dokuwiki/data/pages/techstaff/slurm.txt · Last modified: 2021/01/06 16:13 by kauffman