Platform LSF Administration Guide Version 6.2

Chapter 29
Runtime Resource Usage Limits
Administering Platform LSF
471
Sets the total process virtual memory limit to swap_limit in KB for the whole job. The
default is no limit. Exceeding the limit causes the job to terminate.
This limit applies to the whole job, no matter how many processes the job may contain.
Examples
Queue-level limits ◆ CPULIMIT = 20/hostA 15
The first number is the default CPU limit. The second number is the maximum
CPU limit.
However, the default CPU limit is ignored because it is a higher value than the
maximum CPU limit.
◆ CPULIMIT = 10/hostA
In this example, the lack of a second number specifies that there is no default CPU
limit. The specified number is considered as the default and maximum CPU limit.
◆ RUNLIMIT = 10/hostA 15
The first number is the default run limit. The second number is the maximum run
limit.
The first number specifies that the default run limit is to be used for jobs that are
submitted without a specified run limit (without the
-W option of bsub).
◆ RUNLIMIT = 10/hostA
No default run limit is specified. The specified number is considered as the default
and maximum run limit.
◆ THREADLIMIT=6
No default thread limit is specified. The value 6 is the default and maximum thread
limit.
◆ THREADLIMIT=6 8
The first value (6) is the default thread limit. The second value (8) is the maximum
thread limit.
Job-level limits ◆ % bsub -M 5000 myjob
Submits myjob with a memory limit of 5000 KB.
◆ % bsub -W 14 myjob
myjob
is expected to run for 14 minutes. If the run limit specified with bsub -W
exceeds the value for the queue, the job will be rejected.
◆ % bsub -T 4 myjob
Submits myjob with a maximum number of concurrent threads of 4.