LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 541
Runtime Resource Usage Limits
Resource usage limits specified at job submission must be less than the maximum
specified in
lsb.queues. The job submission is rejected if the user-specified limit
is greater than the queue-level maximum, and the following message is issued:
Cannot exceed queue’s hard limit(s). Job not submitted.
Enforce limits on chunk jobs
By default, resource usage limits are not enforced for chunk jobs because chunk jobs
are typically too short to allow LSF to collect resource usage.
1 To enforce resource limits for chunk jobs, define LSB_CHUNK_RUSAGE=Y
in
lsf.conf. Limits may not be enforced for chunk jobs that take less than a
minute to run.
Scaling the units for resource usage limits
The default unit for the following resource usage limits is KB:
◆ Core limit (-C and CORELIMIT)
◆ Memory limit (-M and MEMLIMIT)
◆ Stack limit (-S and STACKLIMIT)
◆ Swap limit (-v and SWAPLIMIT)
This default may be too small for some environments that make use of very large
resource usage limits, for example, GB or TB.
LSF_UNIT_FOR_LIMITS in
lsf.conf specifies larger units for the resource usage
limits with default unit of KB.
The unit for the resource usage limit can be one of:
◆ KB (kilobytes)
◆ MB (megabytes)
◆ GB (gigabytes)
◆ TB (terabytes)
◆ PB (petabytes)
◆ EB (exabytes)
LSF_UNIT_FOR_LIMITS applies cluster-wide to limts at the job-level (
bsub),
queue-level (
lsb.queues), and application level (lsb.applications).
If ... Then ...
The default limit is not correct The default is ignored and the maximum limit is
enforced
Both default and maximum
limits are specified, and the
maximum is not correct
The maximum is ignored and the resource has no
maximum limit, only a default limit
Both default and maximum
limits are not correct
The default and maximum are ignored and no limit is
enforced