Platform LSF Reference Version 6.2

Limit Section
Platform LSF Reference
434
Limit Section
Sets limits for the maximum amount of the specified resources must be available for
different classes of jobs to start, and which resource consumers the limits apply to.
Limits are enforced during job resource allocation.
For limits to be enforced, jobs must specify rusage resource requirements
(bsub -R or RES_REQ in lsb.queues).
The blimits command displays view current usage of resource allocation limit
configured in
Limit sections in lsb.resources:
Limit section structure
Each set of limits is defined in a Limit section enclosed by Begin Limit and End
Limit
. Limit sections set limits for how much resources must be available for different
classes of jobs to start.
A Limit section has two formats:
◆ Vertical tabular
◆ Horizontal
The file can contain sections in both formats. In either format, you must configure a
limit for at least one consumer and one resource. The Limit section cannot be empty.
Vertical tabular
format
Use the vertical format for simple configuration conditions involving only a few
consumers and resource limits.
The first row consists of the following keywords for:
◆ Resource types:
❖ SLOTS or SLOTS_PER_PROCESSOR
❖ MEM (MB or percentage)
❖ SWP (MB or percentage)
❖ TMP (MB or percentage)
❖ LICENSE
❖ RESOURCE
◆ Consumer types:
❖ USERS or PER_USER
❖ QUEUES or PER_QUEUE
❖ HOSTS or PER_HOST
❖ PROJECTS or PER_PROJECT
Each subsequent row describes the configuration information for resource consumers
and the limits that apply to them. Each line must contain an entry for each keyword. Use
empty parentheses
() or a dash (-) to specify the default value for an entry. Fields
cannot be left blank. For resources, the default is no limit; for consumers, the default is
all consumers.
Multiple entries must be enclosed in parentheses. For RESOURCE and LICENSE limits,
resource and license names must be enclosed in parentheses.