Administering Platform LSF - SAS

Using Historical and Committed Run Time
Limitation
COMMITTED_RUN_TIME_FACTOR can be any positive value between 0.0 and
1.0. The default value is 0.0. As the value of
COMMITTED_RUN_TIME_FACTOR approaches 1.0, more weight is given to
the committed run time in the calculation of the dynamic priority.
If you use queue-level fairshare, and a running job has a committed run time,
you should not switch that job to or from a fairshare queue (using bswitch).
The fairshare calculations will not be correct.
Run time displayed by bqueues and bhpart
The run time displayed by bqueues and bhpart is the sum of the actual,
accumulated run time and the historical run time, but does not include the
committed run time.
Example
The following fairshare parameters are configured in lsb.params:
CPU_TIME_FACTOR = 0
RUN_JOB_FACTOR = 0
RUN_TIME_FACTOR = 1
COMMITTED_RUN_TIME_FACTOR = 1
Without a committed run time factor, dynamic priority for the job owner drops
gradually while a job is running:
232
Administering Platform LSF