Plan-based scheduling run time

Estimating run time of jobs

To make allocation plans, LSF needs estimated run times for all (or most) jobs. To simplify this, the parameter ESTIMATED_RUNTIME can be used to have default estimated run times for classes of jobs.

The ESTIMATED_RUNTIME parameter can be specified at the application level (lsb.applications), the queue level (lsb.queues), or the cluster level (lsb.params). When configured at multiple levels the application-level setting overrides the queue-level setting, which overrides the cluster-level setting.

Alternatively, a job level estimated runtime can be set for a job with the bsub –We command. The job level setting overrides the configured settings for estimated runtime.

If a job does not have an explicit estimated runtime, then the scheduler will estimate the runtime based on the run limit, CPU limit, and termination time. When a job has none of these, the run times is assumed to be infinite.

Viewing the estimated run time of a job

The bjobs –l command displays the estimated run time of a job with the ESTIMATED_RUNTIME section in the output. This output displays the estimated run time, and also how this estimated run time is derived.

Example: Viewing the estimated run time of a job:

username1@intel4-79: bjobs -l 172025

Job <172025>, User <username1>, Project <default>, Status <PEND>, Queue<normal>
                     , Job Priority <500>, Command <x>
Thu Mar 29 15:07:27: Submitted from host <intel4>, CWD <$HOME>, 23 Task(s),Spe
                     cified Hosts <host0>;
 ESTIMATED_RUNTIME:
 10.0 min of intel4 based on user provided runtime estimation.

 PENDING REASONS:
 Not enough processors to meet the job's spanning requirement: 1 host;
 Not specified in job submission: 4607 hosts;
 Closed by LSF administrator: 1 host;

...