Platform LSF Reference Version 6.2

lsb.queues
Platform LSF Reference
401
Job chunking can have the following advantages:
◆ 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 queues 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 in the following kinds of queues:
◆ Interactive (INTERACTIVE=ONLY parameter)
◆ CPU limit greater than 30 minutes (CPULIMIT parameter)
◆ Run limit greater than 30 minutes (RUNLIMIT parameter)
If CHUNK_JOB_DURATION is set in
lsb.params, chunk jobs are accepted
regardless of the value of CPULIMIT or RUNLIMIT.
Example
The following configures a queue named chunk, which dispatches up to 4 jobs in a
chunk:
Begin Queue
QUEUE_NAME = chunk
PRIORITY = 50
CHUNK_JOB_SIZE = 4
End Queue
Default
Undefined
CORELIMIT
Syntax
CORELIMIT=
integer
Description
The per-process (hard) core file size limit (in KB) for all of the processes belonging to a
job from this queue (see
getrlimit(2)).
Default
Unlimited
CPULIMIT
Syntax
CPULIMIT=
[default_limit] maximum_limit
where default_limit and maximum_limit are:
[hour
:]minute[/host_name | /host_model]
Description
Maximum normalized CPU time and optionally, the default normalized CPU time
allowed for all processes of a job running in this queue. 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.