Changes between Version 2 and Version 3 of GridEngine
- Timestamp:
- Dec 8, 2013, 10:14:13 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GridEngine
v2 v3 8 8 9 9 === Job submission === 10 Jobs are submitted with the command !`qsub`. The basic resources that has to be requested are the amount of memory required, and the runtime to allocate to the job. The easiest way to submit jobs is to create a batch file, which contains all commands that should be executed. This file also contains information about job resources and other aspects of how the job should behave. 10 Jobs are submitted with the command !`qsub`. The basic resources that has to be requested are the amount of memory required, and the runtime to allocate to the job. The easiest way to submit jobs is to create a batch file, which contains all commands that should be executed. This file also contains information about job resources and other aspects of how the job should behave. It is good practice to save these job scripts for future reference and to keep track of how you ran your commands. 11 11 12 12 A batch file is basically a script run by the normal command shell. All lines will be executed as if they were typed at the prompt. However, lines beginning with a # will be ignored and are used as comments. Furthermore, lines beginning with #$ will be read by qsub to set options for the job, e.g. resource request. An example could be: … … 52 52 53 53 === Deleting running or queuing jobs === 54 Running jobs can be cancelled with the command 54 Running jobs can be cancelled with the command `qdel JOB_ID`. 55 55 56 56 === Job history === 57 You can get information about resource usage and other metadata regarding finished jobs with the `qacct` command, more specifically`$ qacct -j JOB_ID`.57 You can get information about resource usage and other metadata regarding finished jobs with the `qacct` command, more specifically `$ qacct -j JOB_ID`.