| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:services:application_services:high_performance_computing:running_jobs_slurm [2023/06/21 10:15] – [GPU selection] skrey | en:services:application_services:high_performance_computing:running_jobs_slurm [2024/01/23 15:07] (current) – [Interactive session on the nodes] nboelte |
|---|
| ''<nowiki>--pty</nowiki>'' requests support for an interactive shell, and ''-p medium'' the corresponding partition. ''-c 16'' ensures that you 16 cpus on the node. You will get a shell prompt, as soon as a suitable node becomes available. Single thread, non-interactive jobs can be run with | ''<nowiki>--pty</nowiki>'' requests support for an interactive shell, and ''-p medium'' the corresponding partition. ''-c 16'' ensures that you 16 cpus on the node. You will get a shell prompt, as soon as a suitable node becomes available. Single thread, non-interactive jobs can be run with |
| <code>srun -p medium ./myexecutable</code> | <code>srun -p medium ./myexecutable</code> |
| | |
| | If there is a waiting time for running jobs on the ''medium'' partition, you can use the ''int'' partition for an interactive job that uses CPU resources and ''gpu-int'' for an interactive job that also uses GPU resources. The interactive partitions do not have a waiting time but you do not get any dedicated resources like CPU/GPU cores or Memory but have to share with all other users, so you should not use them for non-interactive jobs. |
| |
| ==== GPU selection ==== | ==== GPU selection ==== |
