This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
guides:slurm:tips [30.04.2020 10:43] Juha Kekäläinen |
guides:slurm:tips [30.04.2020 12:22] Juha Kekäläinen |
||
---|---|---|---|
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 |