Administering Platform LSF - SAS

Usage String
Example
rusage[mem=50:duration=100:decay=1]
This example indicates that 50 MB memory should be reserved for the job. As
the job runs, the amount reserved will decrease at approximately 0.5 MB per
minute until the 100 minutes is up.
How queue-level and job-level rusage sections are resolved
Job-level rusage overrides the queue-level specification:
◆ For internal load indices (r15s, r1m, r15m, ut, pg, io, ls, it, tmp, swp,
and mem), the job-level value cannot be larger than the queue-level value.
◆ For external load indices (e.g., licenses), the job-level rusage can be larger
than the queue-level requirements.
◆ For duration, the job-level value of internal and external load indices
cannot be larger than the queue-level value.
How queue-level and job-level rusage sections are merged
When both job-level and queue-level rusage sections are defined, the rusage
section defined for the job overrides the rusage section defined in the queue.
The two rusage definitions are merged, with the job-level rusage taking
precedence. For example:
◆ Given a RES_REQ definition in a queue:
RES_REQ = rusage[mem=200:lic=1] ...
and job submission:
bsub -R'rusage[mem=100]' ...
The resulting requirement for the job is
rusage[mem=100:lic=1]
where mem=100 specified by the job overrides mem=200 specified by the
queue. However, lic=1 from queue is kept, since job does not specify it.
◆ For the following queue-level RES_REQ (decay and duration defined):
RES_REQ = rusage[mem=200:duration=20:decay=1] ...
and job submission (no decay or duration):
bsub -R'rusage[mem=100]' ...
The resulting requirement for the job is:
rusage[mem=100:duration=20:decay=1]
Queue-level duration and decay are merged with the job-level
specification, and mem=100 for the job overrides mem=200 specified by the
queue. However, duration=20 and decay=1 from queue are kept, since
job does not specify them.
196
Administering Platform LSF