Main Content Region

Slurm Rosetta

Comparison of SLURM with Torque/PBS and Maui commands

Action Slurm Torque/PBS Maui
Get information about the job scontrol show job <jobid> qstat -f <jobid> checkjob
Display the queue information smap/squeue qstat showq
Delete a job scancel <jobid> qdel <jobid>  
Job submission. More details on the Slurm Resource Manger Page srun/sbatch/salloc qsub  
Display the "backfill window" - ie how many processors are currently free     showbf
Display the expected job start times squeue --start   showstart <jobid>
Display information about the queues/partitions available
sinfo qstat -Qf  


Other Notable Differences between SLURM and Torque/PBS

No need for 'cd $PBS_O_WORKDIR'
In SLURM your batch job starts to run in the directory from which you submitted the script whereas in Torque/PBS you need to explicitly move back to that directory with 'cd $PBS_O_WORKDIR'.
No need to manually export environment
The environment variables that are defined in your shell session at the time that you submit the script are exported into your batch job, whereas in Torque/PBS you need to use the '-V' flag to export your environment.
Location of output files
The output and error files are created in their final location immediately that the job begins or an error is generated, whereas in Torque/PBS temporary files are created that are only moved to the final location at the end of the job. Therefore in SLURM you can examine the output and error files from your job during its execution.