Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
habrok:advanced_job_management:running_jobs_on_gpus [2025/09/29 09:25] – [Running interactive jobs] Formatting pedrohabrok:advanced_job_management:running_jobs_on_gpus [2026/06/29 12:46] (current) – [Running interactive jobs] pedro
Line 18: Line 18:
 ==== Available GPU types ==== ==== Available GPU types ====
  
-^ Node ^ GPU type ^  GPUs per node ^  Memory per GPU ^  CPUs per node ^  Memory per node ^ Slurm name ^ +^ Node         ^ GPU type            ^  GPUs per node ^  Memory per GPU ^  CPUs per node ^  Memory per node ^ Slurm name ^ 
-| A100 | Nvidia A100  |  4 |  40 GB |  64 |  512 GB | a100 | +| A100         | Nvidia A100         |  4 |  40 GB |   64 |  512 GB | a100 | 
-| V100 | Nvidia V100  |  2 |  32 GB |  36 |  128 GB | v100 | +| V100         | Nvidia V100         |  2 |  32 GB |   36 |  128 GB | v100 
-| L40S | Nvidia L40S  |  2 |  48 GB |  56 |  512 GB | l40s |+| RTX Pro 6000 | Nvidia RTX Pro 6000 |  8 |  96 GB |  128 |  192 GB | rtx_pro_6000 
 +| L40S         | Nvidia L40S         |  2 |  48 GB |   56 |  512 GB | l40s |
  
 ==== Example ==== ==== Example ====
Line 36: Line 37:
 #SBATCH --gpus-per-node=1 #SBATCH --gpus-per-node=1
 </code> </code>
 +
 +Note that this will only sent jobs to the V100 and A100 nodes. This because not all software is compatible with the RTX  Pro 6000 GPUs. Furthermore the more capable RTX Pro 6000 nodes should not be swamped with jobs that don't need its capabilities. See [[rtx_pro_6000_gpu_nodes]] for more details.
  
 ==== Interactive GPU node ==== ==== Interactive GPU node ====
Line 69: Line 72:
 When the job starts running, you will be automatically logged in to the allocated node, allowing you to run your commands interactively. When you are done, just type ''%%exit%%'' to close your interactive job and to release the allocated resources. When the job starts running, you will be automatically logged in to the allocated node, allowing you to run your commands interactively. When you are done, just type ''%%exit%%'' to close your interactive job and to release the allocated resources.
  
-**N.B.: interactive jobs currently don't (always) use the software stack built for the allocated nodes, you can work around this by first running ''unset SW_STACK_ARCH && module restore'' after the job has started.**+<wrap important>Interactive jobs currently don't (always) use the software stack built for the allocated nodes, you can work around this by first running ''unset SW_STACK_ARCH && module restore'' after the job has started.</wrap>