Checking Grid Resources

Use the Job Utilization View tab to display information that is relevant to a job's consumption of a grid computing resources as well as other elements that factor into a job's dispatch priority. Unlike the Overview view, only running and suspended jobs appear. In the Utilization view, the columns are as follows:

Figure 5–2 Job Utilization View Tab

• State – The Job State is indicated by the following letters:

  • d (deletion) – Indicates that a job has been deleted (using qdel).

  • r (running) – Indicates that a job is about to be executed or is already executing

  • R (restarted) – Indicates that the job was restarted. This can be caused by a job migration or because of one of the reasons described in the -r section of the qsub(1) command.

  • s (suspended) – Shows that an already running job has been suspended (using qmod(1))..

  • S (suspended) – Show that an already running job has been suspended because the queue that it belongs to has been suspended.

  • t (transferring) – Indicates that a job is about to be executed or is already executing.

  • T (threshold) – Show that an already running job has been suspended because at least one suspend threshold of the corresponding queue was exceeded (see queue_conf(5)) and that the job has been suspended as a consequence.

  • w (waiting) – Indicates that the job is suspended pending the availability of a critical resource or specified condition.

  See the qstatman page for a detailed explanation about these state conditions. For more information, you can also see Monitoring and Controlling Jobs and Queues in the N1 Grid Engine User manual.

• ID – The job ID provides a unique identity and also a method of accessing the Job Details page.

• Name – The name of the job. Assigning names to jobs makes them more comprehensible and easier to track than just relying on job IDs.

• Queue – The queue instance which this the job belongs to.

• CPU – The amount of CPU time that the job has consumed.

• Memory – The amount of memory that the job is using.

• Share – The calculated share of the total system to which the job is entitled currently.

• Run time – The length of time the job has been running since it was dispatched.

• NTickets – The normalized Ticket priority. You can use the Override component of the ticket policy to increase the entitlement of a specific User, Project, or Department. By assigning Override Tickets, you can modify the entitlement without affecting any prioritization assignments of the Urgency policy.

• NUrgency – The normalized Urgency priority. Three factors contribute to this priority: the deadline contribution, the wait-time contribution, and the resource requirement contribution.

• NPOSIX – The normalized POSIX priority. An administrator can use this value to arbitrarily increase the priority of certain jobs.

• Task – The currently executing task. Some jobs consist of a single task, in which case, the task ID is always 1. However, parallel jobs and array jobs each consist of more than one task. The tasks are usually numbered in ascending order starting with 1. Depending upon how the job was submitted, sometimes the numbers might skip, (1,3,5,). On running jobs, each task runs distinctly and so has its own configuration information, environment, and trace. For details about the task, click the task number to display the Task Details page.

If the CPU usage or memory usage values are blank, the usage information for that job has not yet been reported. Check back at a later time to see if the usage is then reported.

For more information on the meaning of each column, see the QMON man page.

Normalized Priorities

The normalized ticket, urgency, and POSIX priorities are the three top level policies used by the N1GE Scheduler to determine a job's dispatch priority. Each calculate a factor that contributes to the overall priority. In order for these three policy contributions to be added together in a meaningful way, they are each normalized to a number between 0 and 1.