Administering Platform LSF - SAS

Supported Resource Usage Limits and Syntax
Format
Normalized run
time
Platform
MultiCluster
Thread limit
run_limit is in the form [hour:]minute, where minute can be greater than
59. 3.5 hours can either be specified as 3:30 or 210.
The run time limit is normalized according to the CPU factor of the
submission host and execution host. The run limit is scaled so that the job has
approximately the same run time for a given run limit, even if it is sent to a
host with a faster or slower CPU.
For example, if a job is submitted from a host with a CPU factor of 2 and
executed on a host with a CPU factor of 3, the run limit is multiplied by 2/3
because the execution host can do the same amount of work as the submission
host in 2/3 of the time.
If the optional host name or host model is not given, the run limit is scaled
based on the DEFAULT_HOST_SPEC specified in the lsb.params file. (If
DEFAULT_HOST_SPEC is not defined, the fastest batch host in the cluster is
used as the default.) If host or host model is given, its CPU scaling factor is
used to adjust the actual run limit at the execution host.
The following example specifies that myjob can run for 10 minutes on a
DEC3000 host, or the corresponding time on any other host:
% bsub -W 10/DEC3000 myjob
If ABS_RUNLIMIT=Y is defined in lsb.params, the run time limit is not
normalized by the host CPU factor. Absolute wall-clock run time is used for all
jobs submitted with a run limit.
See “CPU Time and Run Time Normalization” on page 357 for more
information.
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). The ABS_RUNLIMIT
parameter in lsb.params is is not supported in either MultiCluster model; run
time limit is normalized by the CPU factor of the execution host.
Job syntax (bsub) Queue syntax (lsb.queues) Fomat/Units
-T thread_limit THREADLIMIT=[default] maximum integer
Sets the limit of the number of concurrent threads to thread_limit for the
whole job. The default is no limit.
Exceeding the limit causes the job to terminate. The system sends the following
signals in sequence to all processes belongs to the job: SIGINT, SIGTERM, and
SIGKILL.
If a default thread limit is specified, jobs submitted to the queue without a joblevel
thread limit are killed when the default thread limit is reached.
If you specify only one limit, it is the maximum, or hard, thread limit. If you
specify two limits, the first one is the default, or soft, thread limit, and the
second one is the maximum thread limit.
354
Administering Platform LSF