rsnt_translations
56,420
edits
Running jobs: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 51: | Line 51: | ||
<!--T:106--> | <!--T:106--> | ||
Memory may be requested with <code>--mem-per-cpu</code> (memory per core) or <code>--mem</code> (memory per node). On general-purpose (GP) clusters a default memory amount of 256 MB per core will be allocated unless you make some other request. On [[Niagara]], only whole nodes are allocated along with all available memory, so a memory specification is not required there. | Memory may be requested with <code>--mem-per-cpu</code> (memory per core) or <code>--mem</code> (memory per node). On general-purpose (GP) clusters, a default memory amount of 256 MB per core will be allocated unless you make some other request. On [[Niagara]], only whole nodes are allocated along with all available memory, so a memory specification is not required there. | ||
<!--T:162--> | <!--T:162--> | ||
| Line 220: | Line 220: | ||
<!--T:29--> | <!--T:29--> | ||
You can start an interactive session on a compute node with [https://slurm.schedmd.com/salloc.html salloc]. In the following example we request two tasks, which corresponds to two CPU cores and | You can start an interactive session on a compute node with [https://slurm.schedmd.com/salloc.html salloc]. In the following example we request two tasks, which corresponds to two CPU cores and 3 GB of memory, for an hour: | ||
$ salloc --time=1:0:0 --mem=3G --ntasks=2 --account=def-someuser | $ salloc --time=1:0:0 --mem=3G --ntasks=2 --account=def-someuser | ||
salloc: Granted job allocation 1234567 | salloc: Granted job allocation 1234567 | ||
| Line 262: | Line 262: | ||
<!--T:169--> | <!--T:169--> | ||
Output from a non-interactive Slurm job is normally <i>buffered</i>, which means that there is usually a delay between when data is written by the job and when you can see the output on a login node. Depending on the application you are running and the load on the filesystem, this delay can range from less than a second to many minutes, or until the job completes. | Output from a non-interactive Slurm job is normally <i>buffered</i>, which means that there is usually a delay between when data is written by the job and when you can see the output on a login node. Depending on the application, you are running and the load on the filesystem, this delay can range from less than a second to many minutes, or until the job completes. | ||
<!--T:170--> | <!--T:170--> | ||