User Tools
running_jobs
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
running_jobs [2021/10/22 12:42] root |
running_jobs [2021/10/22 12:46] (current) root |
||
|---|---|---|---|
| Line 44: | Line 44: | ||
| You should use the **-c** option if you are running a job that allows you to specify how many threads to run (or cores to use). So, if you have an option on the program you are running to say "use 8 cores" you should also tell SLURM that your program is using 8 cores. If you don't do this, your job will only be allowed to use 1 core (and the threads started by your program will be time-sliced on that one core, probably making it run much slower than you expected). | You should use the **-c** option if you are running a job that allows you to specify how many threads to run (or cores to use). So, if you have an option on the program you are running to say "use 8 cores" you should also tell SLURM that your program is using 8 cores. If you don't do this, your job will only be allowed to use 1 core (and the threads started by your program will be time-sliced on that one core, probably making it run much slower than you expected). | ||
| + | |||
| + | ---- | ||
| + | |||
| + | === --exclusive === | ||
| + | |||
| + | Request all the cores on a node. This will set the allocation of cores on that node to however many cores there are in total on the node. Since you likely want all the memory on the node as well, you should likely specify " | ||
| + | |||
| + | ---- | ||
| + | |||
| + | === --mem === | ||
| + | |||
| + | Use the --mem option to request memory for your job. e.g. --mem=25G will request 25GB of RAM. You can, and should, request less than your default allocation of 8GB if you don't need 8GB. This frees up that memory for other users. | ||
| + | |||
| + | " | ||
| === -n, --ntasks === | === -n, --ntasks === | ||
| Line 66: | Line 80: | ||
| But, for sbatch, it will be up to your task to make sure that core is actually used. For srun, your task will be run as many times as nodes you specified: it will be up to you to make sure your tasks don't all do exactly the same thing. | But, for sbatch, it will be up to your task to make sure that core is actually used. For srun, your task will be run as many times as nodes you specified: it will be up to you to make sure your tasks don't all do exactly the same thing. | ||
| - | |||
| - | ---- | ||
| - | |||
| - | === --exclusive === | ||
| - | |||
| - | Request all the cores on a node. This will set the allocation of cores on that node to however many cores there are in total on the node. Since you likely want all the memory on the node as well, you should likely specify " | ||
| ---- | ---- | ||
running_jobs.1634920925.txt.gz ยท Last modified: 2021/10/22 12:42 by root
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain
