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
en:services:application_services:high_performance_computing:interactive_queue [2019/04/08 13:51]
tehlers
en:services:application_services:high_performance_computing:interactive_queue [2019/06/12 13:13] (current)
mboden -n to -c
Line 12: Line 12:
 For an interactive bash session: For an interactive bash session:
 <​code>​ <​code>​
-srun -p int --pty bash+srun -p int -c 20 -N 1 --pty bash
 </​code>​ </​code>​
 For an interactive bash session with X-Windows (GUI) support: For an interactive bash session with X-Windows (GUI) support:
 <​code>​ <​code>​
-srun --x11 -p int --pty bash+srun --x11 -c 20 -N 1 -p int --pty bash
 </​code>​ </​code>​
 For an interactive session with MPI support: For an interactive session with MPI support:
 <​code>​ <​code>​
-srun -p int -n 80 --ntasks-per-node=20 --pty bash+srun -p int -N 4 --ntasks-per-node=20 --pty bash
 </​code>​ </​code>​
 You can also use these commands with a standard queue, for example to set some parameters interactively at the beginning of a long running job. You can also use these commands with a standard queue, for example to set some parameters interactively at the beginning of a long running job.
Line 26: Line 26:
 The default walltime in this queue is **1 hour**, you can extend the walltime to a maximum of 12 hours, by using "​-t"​. The default walltime in this queue is **1 hour**, you can extend the walltime to a maximum of 12 hours, by using "​-t"​.
  
-Note that **only in the int queue** you are allowed to use more cores than you asked for.+**NEED REVIEW FOR SLURM:**
  
-NEED REVIEW FOR SLURM: +Note that **only in the int queue** you are allowed to use more cores than you asked for. However, mpirun will always start the number of processes specified with srun. While you can also use other means (like mpiexec) to start MPI jobs in the int queue, processes running on a node not participating in your interactive job will be automatically killed.
-However, mpirun will always start the number of processes specified with srun. While you can also use other means (like mpiexec) to start MPI jobs in the int queue, processes running on a node not participating in your interactive job will be automatically killed.+