LSF Version 7.3 - Platform LSF Configuration Reference

Description
Normalized CPU time allowed for all processes of a job running in the application profile. The
name of a host or host model specifies the CPU time normalization host to use.
Limits the total CPU time the job can use. This parameter is useful for preventing runaway
jobs or jobs that use up too many resources.
When the total CPU time for the whole job has reached the limit, a SIGXCPU signal is sent
to all processes belonging to the job. If the job has no signal handler for SIGXCPU, the job is
killed immediately. If the SIGXCPU signal is handled, blocked, or ignored by the application,
then after the grace period expires, LSF sends SIGINT, SIGTERM, and SIGKILL to the job to
kill it.
If a job dynamically spawns processes, the CPU time used by these processes is accumulated
over the life of the job.
Processes that exist for fewer than 30 seconds may be ignored.
By default, jobs submitted to the application profile without a job-level CPU limit (bsub -
c) are killed when the CPU limit is reached. Application-level limits override any default limit
specified in the queue.
The number of minutes may be greater than 59. For example, three and a half hours can be
specified either as 3:30 or 210.
If no host or host model is given with the CPU time, LSF uses the default CPU time
normalization host defined at the queue level (DEFAULT_HOST_SPEC in lsb.queues) if
it has been configured, otherwise uses the default CPU time normalization host defined at the
cluster level (DEFAULT_HOST_SPEC in lsb.params) if it has been configured, otherwise
uses the host with the largest CPU factor (the fastest host in the cluster).
On Windows, a job that runs under a CPU time limit may exceed that limit by up to
SBD_SLEEP_TIME. This is because sbatchd periodically checks if the limit has been exceeded.
On UNIX systems, the CPU limit can be enforced by the operating system at the process level.
You can define whether the CPU limit is a per-process limit enforced by the OS or a per-job
limit enforced by LSF with LSB_JOB_CPULIMIT in lsf.conf.
Default
Unlimited
DATALIMIT
Syntax
DATALIMIT=integer
Description
The per-process (soft) data segment size limit (in KB) for all of the processes belonging to a
job running in the application profile (see getrlimit(2)).
By default, jobs submitted to the application profile without a job-level data limit (bsub -D)
are killed when the data limit is reached. Application-level limits override any default limit
specified in the queue, but must be less than the hard limit of the submission queue.
lsb.applications
164 Platform LSF Configuration Reference