LSF Version 7.3 - Platform LSF Configuration Reference

Description
The maximum run limit and optionally the default run limit. The name of a host or host model
specifies the runtime normalization host to use.
By default, jobs that are in the RUN state for longer than the specified maximum run limit are
killed by LSF. You can optionally provide your own termination job action to override this
default.
Jobs submitted with a job-level run limit (bsub -W) that is less than the maximum run limit
are killed when their job-level run limit is reached. Jobs submitted with a run limit greater
than the maximum run limit are rejected by the queue.
If a default run limit is specified, jobs submitted to the queue without a job-level run limit are
killed when the default run limit is reached. The default run limit is used with backfill
scheduling of parallel jobs.
Note:
If you want to provide an estimated run time for scheduling
purposes without killing jobs that exceed the estimate, define the
RUNTIME parameter in an application profile instead of a run limit
(see lsb.applications for details).
If you specify only one limit, it is the maximum, or hard, run limit. If you specify two limits,
the first one is the default, or soft, run limit, and the second one is the maximum run limit.
The number of minutes may be greater than 59. Therefore, three and a half hours can be
specified either as 3:30, or 210.
The run limit is in the form of [hour:]minute. The minutes can be specified as a number greater
than 59. For example, three and a half hours can either be specified as 3:30, or 210.
The run limit you specify is the normalized run time. This is done so that the job does
approximately the same amount of processing, even if it is sent to host with a faster or slower
CPU. Whenever a normalized run time is given, the actual time on the execution host is the
specified time multiplied by the CPU factor of the normalization host then divided by the CPU
factor of the execution host.
If ABS_RUNLIMIT=Y is defined in lsb.params, the runtime limit is not normalized by the
host CPU factor. Absolute wall-clock run time is used for all jobs submitted to a queue with
a run limit configured.
Optionally, you can supply a host name or a host model name defined in LSF. You must insert
‘/’ between the run limit and the host name or model name. (See lsinfo(1) to get host model
information.)
If no host or host model is given, LSF uses the default runtime normalization host defined at
the queue level (DEFAULT_HOST_SPEC in lsb.queues) if it has been configured;
otherwise, LSF uses the default CPU time normalization host defined at the cluster level
(DEFAULT_HOST_SPEC in lsb.params) if it has been configured; otherwise, the host with
the largest CPU factor (the fastest host in the cluster).
For MultiCluster jobs, if no other CPU time normalization host is defined and information
about the submission host is not available, LSF uses the host with the largest CPU factor (the
fastest host in the cluster).
Jobs submitted to a chunk job queue are not chunked if RUNLIMIT is greater than 30 minutes.
lsb.queues
Platform LSF Configuration Reference 317