guides:slurm:tips
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
guides:slurm:tips [30.04.2020 10:42] Juha Kekäläinen |
guides:slurm:tips [15.11.2021 16:19] (current) Administrator |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| With SLURM for your own sake it is important not to overallocate the resources while pending time slot for the computing job. If you overallocate then your job will be pending for resources for a long time. | With SLURM for your own sake it is important not to overallocate the resources while pending time slot for the computing job. If you overallocate then your job will be pending for resources for a long time. | ||
| - | For example if you request 50 GB of RAM for you computing job while it actually uses 5 GB. Then the job will wait for computing slot for 50 GB of job and this could mean that you will wait computing time for multiple days. Or if you running parallel | + | For example if you request 50 GB of RAM for you computing job while it actually uses 5 GB. Then the job will wait for computing slot for 50 GB of job and this could mean that you will wait computing time for multiple days. Or if you are running |
| - | Other users will suffer while they are waiting for computing resources that are reserved for no reason. | + | Other users also will suffer while they are waiting for computing resources that are reserved for no reason. |
| ## Use local SSD of the computing node | ## Use local SSD of the computing node | ||
| - | Each computing node has 400 GB of local storage and it is mounted to the /tmp path. For the computing jobs that write temporary results you could get much greater performance by using the local storage instead of the network drive. | + | Each computing node has 300 GB of local storage and it is mounted to the /tmp path. For the computing jobs that write temporary results you could get much greater performance by using the local storage instead of the network drive. |
| ## Monitor your jobs | ## Monitor your jobs | ||
| Line 21: | Line 21: | ||
| You should also check the Slurm job efficiency report for the completed jobs. This way you will find out how much was your CPU, memory and wall time usage. With these informations you can fine tune your jobs and not overallocate the computing cluster. | You should also check the Slurm job efficiency report for the completed jobs. This way you will find out how much was your CPU, memory and wall time usage. With these informations you can fine tune your jobs and not overallocate the computing cluster. | ||
| - | ´´´ | + | ``` |
| seff JOBID | seff JOBID | ||
| Line 36: | Line 37: | ||
| Memory Efficiency: 16.42% of 62.50 GB | Memory Efficiency: 16.42% of 62.50 GB | ||
| - | ´´´ | + | ``` |
guides/slurm/tips.1588232556.txt.gz · Last modified: 30.04.2020 10:42 by Juha Kekäläinen