Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Jobs submitted to Gadi are given a jobID, this is shown to you as soon as it has been accepted and is a string of eight numbers, e.g. 12345678. NCI encourages users to monitor their jobs at every stage, to monitor it's health and assist in detecting errors and failures. However, please refrain from checking your jobs excessively. Repeated queries will be considered attacks, especially in quick succession. Our recommendation is to query your jobs status a maximum of once every 10 minutes, this should be more than enough. |
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Anchor | ||||
---|---|---|---|---|
|
Panel | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Queue Status
| ||||||||||||||||||
Anchor |
| status
| |||||||||||||||||
Queue status |
Code Block | ||
---|---|---|
| ||
$ qstat -swx <jobID> |
The command -swx
is made up of:
-s
: Summary format - shows queue level status rather than individual jobs
-w:
Wide format - displays output in multiple columns
-x:
Extended/Expanded format - includes additional details in the output
The screenshot below is in regards to job 12345678.gadi -pbs
aaa777
submitted the jobnormal-exec
queue48 cores
and 190 GiB memory
2697
, and the space reserved on jobfs
You can go even further with this and run the command
Code Block | ||
---|---|---|
| ||
$ qstat -fx <jobID> | less |
In this case, -f
means full/full information, by combining this with -x
, we can print the complete job information.
If you would like to see a list of qstat
commands and their functions, please check the qstat manual
by running
Code Block | ||
---|---|---|
| ||
$ man qstat |
Anchor | ||||
---|---|---|---|---|
|
Panel | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Anchor |
| CPU and Memory Utilisation
| ||||||||||||||
Users should continue to monitor their jobs, especially the utilisation rate. If users run into errors, this will be evident in a drop in utilisation rate. While a low utilisation rate is helpful for spotting the underuse of compute time, a 100% utilisation rate doesn't necessarily indicate the most efficient use of requested resources. Further enquiries can be made to check if performance can be improved. To see how much CPU and memory your job has actually been using, run the command
This show us that the CPU ran at only 23% of the compute capacity of the 48 cores that were requested and that 36:47 has elapsed. It also shows the peak memory usage in the columns RSS and MEM. Depending on the tasks running within this job, the percentage may increase as its lifespan continues. NCI recommends that users aim for at least 80% overall CPU utilisation rate. |
Anchor | ||||
---|---|---|---|---|
|
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Process Status in JobTo monitor the status of processes taking place inside a job, you can take a snapshot of the process status of a job by running
|
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
To list the files contained in the |
folder
To copy a file from $PBS_JOBFS into your current folder, you can use the command
|
Commands to help monitor you your jobs | |
man qstat | View the manual for qstat and a range of helpful commands |
qdel <jobid> | Delete the job with jobID <jobid> |
qstat -swx <jobid> | Display the job status in the queue with comment |
qstat -fx <jobid> | Display full job status information |
qps <jobid> | Take a snapshot of the process status of all current processes in the running job |
qcat [-s/-o/-e] <jobid> | Display [submission script/STDOUT/STDERR] of the running job |
qls <jobid> | List contents in the folder $PBS_JOBFS |
qcp <jobid> <dst> | Copy files and directories from the folder $PBS_JOBFS to the destination folder <dst> |
theme | FadeToGrey |
---|