LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 289
Specifying Resource Requirements
◆ By default, duration is specified in minutes. For example, the following specify
a duration of 1 hour:
❖ duration=60
❖ duration=1h
❖ duration=3600s
TIP: Duration is not supported for static shared resources. If the shared resource is
defined in an lsb.resources Limit section, then duration is not applied.
Decay The decay value indicates how the reserved amount should decrease over the
duration.
◆ A value of 1 indicates that system should linearly decrease the amount reserved
over the duration.
◆ A value of 0 causes the total amount to be reserved for the entire duration.
Values other than 0 or 1 are unsupported. If duration is not specified, decay value
is ignored.
TIP: Decay is not supported for static shared resources. If the shared resource is defined in an
lsb.resources Limit section, then decay is not applied.
Default If a resource or its value is not specified, the default is not to reserve that resource.
If duration is not specified, the default is to reserve the total amount for the lifetime
of the job. The default decay value is 0.
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]" ...