LSF Version 7.3 - Platform LSF Configuration Reference

•
Reduces communication between sbatchd and mbatchd and reduces scheduling overhead
in mbschd.
•
Increases job throughput in mbatchd and CPU utilization on the execution hosts.
However, throughput can deteriorate if the chunk job size is too big. Performance may decrease
on profiles with CHUNK_JOB_SIZE greater than 30. You should evaluate the chunk job size
on your own systems for best performance.
With MultiCluster job forwarding model, this parameter does not affect MultiCluster jobs
that are forwarded to a remote cluster.
Compatibility
This parameter is ignored and jobs are not chunked under the following conditions:
•
CPU limit greater than 30 minutes (CPULIMIT parameter in lsb.queues or
lsb.applications)
•
Run limit greater than 30 minutes (RUNLIMIT parameter in lsb.queues or
lsb.applications)
•
Runtime estimate greater than 30 minutes (RUNTIME parameter in
lsb.applications)
If CHUNK_JOB_DURATION is set in lsb.params, chunk jobs are accepted regardless of
the value of CPULIMIT, RUNLIMIT or RUNTIME.
Default
Not defined
CORELIMIT
Syntax
CORELIMIT=integer
Description
The per-process (soft) core file size limit for all of the processes belonging to a job from this
application profile (see getrlimit(2)). Application-level limits override any default limit
specified in the queue, but must be less than the hard limit of the submission queue. Job-level
core limit (bsub -C) overrides queue-level and application-level limits.
By default, the limit is specified in KB. Use LSF_UNIT_FOR_LIMITS in lsf.conf to specify
a larger unit for the the limit (MB, GB, TB, PB, or EB).
Default
Unlimited
CPULIMIT
Syntax
CPULIMIT=[[hour:]minute[/host_name | /host_model]
lsb.applications
Platform LSF Configuration Reference 163