Difference between revisions of "Torque"

From HPC Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
== General ==
 
== General ==
  
Torque is a job [[Scheduler|scheduler]]. It is used to monitor and control the workload of the batch system of a supercomputer and assigns resources to jobs. This system targets applications that utilize a lot of resources and it cannot be directly accessed by the user, as opposed to the [[Nodes#Log-in|login-nodes]].
+
Torque is a job [[Scheduler|scheduler]]. It is used to monitor and control the workload of the batch system of a supercomputer and assigns resources to jobs. This system targets applications that utilize a lot of resources and it cannot be directly accessed by the user, as opposed to the [[Nodes#Log-in|login-nodes]]. Applications to execute have to be specified in a [[Jobscript|jobscript]] that is sent to the batch system by the user.
  
  

Revision as of 12:50, 29 March 2018

General

Torque is a job scheduler. It is used to monitor and control the workload of the batch system of a supercomputer and assigns resources to jobs. This system targets applications that utilize a lot of resources and it cannot be directly accessed by the user, as opposed to the login-nodes. Applications to execute have to be specified in a jobscript that is sent to the batch system by the user.


Job Submission

This command submits the job you defined in your jobscript to the batch system:

$ qsub jobscript.sh

Just like any other incoming job, your job will first be queued. Then, the scheduler decides when your job will be run. The more resources your job requires, the longer it may be waiting to execute.

You can check the current status of your submitted jobs and their job ids with the following shell command. The most common states for a job are "pend", "run", "queue" (Que) or "on hold" (Hold). The command also shows the elapsed time since your job has started running and the time limit.

$ qstat -u <user_id>

In case you submitted a job on accident or realised that your job might not be running correctly, you can always remove it from the queue or terminate it when running by typing:

$ qdel <job_id>