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 [2017/10/10 11:18]
tehlers
en:services:application_services:high_performance_computing:interactive_queue [2019/06/12 13:13] (current)
mboden -n to -c
Line 1: Line 1:
-The interactive ​queue ''​int''​ is meant for interactive jobs, i.e.,+The interactive ​partition ​''​int''​ is meant for interactive jobs, i.e.,
  
   * jobs that require constant user interaction (like Mathematica or other GUI oriented packages),   * jobs that require constant user interaction (like Mathematica or other GUI oriented packages),
Line 8: Line 8:
 The special property of this queue is that the participating nodes have no slot limit. They will take jobs until their load crosses a specified threshold. This accommodates the fact that interactive job cores are not used constantly. The special property of this queue is that the participating nodes have no slot limit. They will take jobs until their load crosses a specified threshold. This accommodates the fact that interactive job cores are not used constantly.
  
-Submitting interactive jobs works as follows (sessions started without ​bsub will be automatically killed):+Submitting interactive jobs works as follows (sessions started without ​srun will be automatically killed):
  
 For an interactive bash session: For an interactive bash session:
 <​code>​ <​code>​
-bsub -ISs -q int /bin/bash+srun -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>​
-bsub -ISs -XF -int /bin/bash+srun --x11 -c 20 -N 1 -p int --pty bash
 </​code>​ </​code>​
-For an interactive session with Intel MPI support:+For an interactive session with MPI support:
 <​code>​ <​code>​
-bsub -ISs -q int -a intelmpi -n 4 -R "​span[ptile=1]" /bin/bash+srun -int -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.
  
-The default walltime in this queue is **1 hour**, you can extend the walltime to a maximum of 12 hours, by using "-W".+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. However, mpirun.lsf will always start the number of processes specified with bsub. 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.+**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.