techstaff:slurm
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| techstaff:slurm [2015/12/29 16:28] – [Storage] kauffman | techstaff:slurm [2016/01/04 16:46] – kauffman | ||
|---|---|---|---|
| Line 8: | Line 8: | ||
| 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 ===== | ||
| + | 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 | ||
| + | |||
| ===== Documentation ===== | ===== Documentation ===== | ||
/var/lib/dokuwiki/data/pages/techstaff/slurm.txt · Last modified: 2021/01/06 16:13 by kauffman