Administering Platform LSF - SAS

Chapter 26
Runtime Resource Usage Limits
OS memory limit
enforcement
Process limit
On UNIX, the time interval between SIGINT, SIGKILL, SIGTERM can be
configured with the parameter JOB_TERMINATE_INTERVAL in lsb.params.
OS enforcement usually allows the process to eventually run to completion.
LSF passes mem_limit to the OS which uses it as a guide for the system
scheduler and memory allocator. The system may allocate more memory to a
process if there is a surplus. When memory is low, the system takes memory
from and lowers the scheduling priority (re-nice) of a process that has
exceeded its declared mem_limit.
OS memory limit enforcement is only available on systems that support
RLIMIT_RSS for setrlimit().
The following operating systems do not support the memory limit at the OS
level:
◆ Windows NT
◆ Sun Solaris 2.x
Run time limit
Job syntax (bsub) Queue syntax (lsb.queues) Fomat/Units
-p process_limit PROCESSLIMIT=[default] maximum integer
Sets the limit of the number of processes to process_limit for the whole job.
The default is no limit. Exceeding the limit causes the job to terminate.
Limits the number of concurrent processes that can be part of a job.
If a default process limit is specified, jobs submitted to the queue without a
job-level process limit are killed when the default process limit is reached.
If you specify only one limit, it is the maximum, or hard, process limit. If you
specify two limits, the first one is the default, or soft, process limit, and the
second one is the maximum process limit.
Job syntax (bsub) Queue syntax (lsb.queues) Fomat/Units
-W run_limit RUNLIMIT=[default] maximum [hours:]minutes[
/host_name |
/host_model]
A run time limit is the maximum amount of time a job can run before it is
terminated. It sets the run time limit of a job. The default is no limit. If the
accumulated time the job has spent in the RUN state exceeds this limit, the job
is sent a USR2 signal. If the job does not terminate within 10 minutes after
being sent this signal, it is killed.
With deadline constraint scheduling configured, a run limit also specifies the
amount of time a job is expected to take, and the minimum amount of time
that must be available before a job can be started.
Jobs submitted to a chunk job queue are not chunked if the run limit is greater
than 30 minutes.
Administering Platform LSF 353