Documentation

Listing Jobs

The optimization jobs running on a Compute Server cluster can be listed using the jobs command:

> grbcluster jobs
JOBID    ADDRESS  STATUS  #Q  STIME               USER  PRIO API
58780a22 server1  RUNNING     2019-04-07 14:36:49 jones 0    gurobi_cl

The jobs command is actually a shortcut for the job list command.

> grbcluster job list
JOBID    ADDRESS  STATUS  #Q  STIME               USER  PRIO API
58780a22 server1  RUNNING     2019-04-07 14:36:49 jones 0    gurobi_cl

Note that you can get more information by using the --long flag. With this flag, you will also display the complete job ID, which is unique, instead of the short ID:

> grbcluster jobs --long
JOBID        ADDRESS  STATUS  #Q  STIME               USER  PRIO API       RUNTIME PID   HOST   IP
58780a22-... server1  RUNNING     2019-04-07 14:36:49 jones 0    gurobi_cl 8.1.1   20656 machine1 [::1]

The jobs command only shows jobs that are currently running. To obtain information on jobs that were processed recently, run the job recent command:

> grbcluster job recent
JOBID    ADDRESS  STATUS    STIME               USER  OPT         API
58780a22 server1  COMPLETED 2019-04-07 14:36:54 jones OPTIMAL     gurobi_cl

The information displayed by the jobs and job recent commands can be changed using the --view flag. The default view for the two commands is the status view. Alternatives are:

status   - List all jobs and their statuses
model    - List all jobs, and include information about the models solved
simplex  - List jobs that used the SIMPLEX algorithm
barrier  - List jobs that used the BARRIER algorithm
mip      - list jobs that used the MIP algorithm

For example, the model view gives details about the model, including the number of rows, columns and nonzeros in the constraint matrix:

> grbcluster job recent --view=model
JOBID    STATUS    STIME               ROWS COLS NONZ ALG OBJ  DURATION
58780a22 COMPLETED 2019-04-07 14:36:54 331  45   1034 MIP 30   4.901s

To get an explanation of the meanings of the different fields within a view, add the --describe flag. For example:

> grbcluster job recent --view=model --describe
JOBID     - Unique job ID, use --long to display full ID
STATUS    - Job status
STIME     - Job status updated time
ROWS      - Number of rows
COLS      - Number of columns
NONZ      - Number of non zero
ALG       - Algorithm MIP, SIMPLEX or BARRIER
OBJ       - Best objective
DURATION  - Solve duration

For a Mixed-Integer Program (MIP), the mip view provides progress information for the branch-and-cut tree. For example:

> grbcluster job recent --view=mip
JOBID    STATUS    STIME               OBJBST OBJBND NODCNT SOLCNT CUTCNT NODLFT
58780a22 COMPLETED 2019-04-07 14:36:54 30     30     54868  4      19     0

Again, --describe explains the meanings of the different fields:

> grbcluster job recent --view mip --describe
JOBID     - Unique job ID, use --long to display full ID
STATUS    - Job status
STIME     - Job status updated time
OBJBST    - Current best objective
OBJBND    - Current best objective bound
NODCNT    - Current explored node count
SOLCNT    - Current count of feasible solutions found
CUTCNT    - Current count of cutting planes applied
NODLFT    - Current unexplored node count

Note that the jobs command provides live status information, so you will for example see current MIP progress information while the solve is in progress.

The other views (simplex and barrier) are similar, although of course they provide slightly different information.