Sge:qsub/qstat/qdel/qhost mission delivery and monitoring

Reference:

Oracle Grid Engine

Qsub command

Sge-qsub usage Examples

Basic usage of SGE job

Qsub is the most stable underlying mission delivery system, which is to deliver a script to the cluster's compute nodes.

Note that only the login node is eligible to deliver the task, the compute node does not have permission to deliver the task, can only execute, so do not in the delivery script nested delivery, will error.

Here are my most commonly used delivery commands:

Qsub-cwd-l vf=5g-p Task Unit-q queue name

Explain first-by-article:

-CWD: It is current working directory, which starts the job from the present directory, that is, the log file will be written to the current directory, and if it is not, it will be output to the user's home directory by default. If you want to specify an output directory, you can use the WD command, and log will output to the directory you specify.

-l:resource=value, indicating the resources required for the job to run. You can see that we have specified the estimated memory vf=5g, and we don't normally specify the number of CPUs. Notice, the actual this no egg use, very few clusters can strictly limit the user's memory use, VF will only affect the efficiency of your delivery, someone will be loopholes, as far as possible to lower the memory to vote, as soon as possible. This part is actually a moral constraint.

-P: Large organizations will be divided into teams, sub-projects, different projects need to develop the project name, mainly for the latter to facilitate statistical calculation of the consumption of resources, calculate money, in fact, this command no eggs.

-Q: Specifies the queue name, this is very important, the queue is the computer's queue, a queue only a few specific compute nodes, you cast a node, you can only use the compute resources specified by the node.

To be Continued ~

Sge:qsub/qstat/qdel/qhost mission delivery and monitoring