LSF Version 7.3 - Using Platform LSF HPC

By default, the per-processor job slot limit is 1 (PJOB_LIMIT=1 in the rms queue in
lsb.queues).
Do not change this default.
If LSF operates on a large system (for example, a system with more than 32 hosts), you
may need to configure the parameter MAX_SBD_CONNS in
lsb.params.
MAX_SBD_CONNS controls the maximum number of files
mbatchd can have open
and connected to
sbatchd.
In a very busy cluster with many jobs being dispatched, running, finishing at the same
time, you may see it takes a very long time for
mbatchd to update the status change of
a job, and to dispatch new jobs. If your cluster shows this behavior, you should set
MAX_SBD_CONNS = (number_of_hosts) * 2 or 300, which ever is less. Setting
MAX_SBD_CONNS too high may slow down the speed of
mbatchd dispatching new
jobs.
About job limits and configuring hosts and queues, see Administering
Platform LSF
About the bqueues command and the lsb.hosts, lsb.params, and
lsb.queues files, see the Platform LSF Configuration Guide
Configuring default and mandatory topology scheduling options
Use the DEFAULT_EXTSCHED and MANDATORY_EXTSCHED queue
paramters in
lsb.queues to configure default and mandatory topology scheduling
options.
DEFAULT_EXTSCHED=RMS[ allocation_type ;topology ;flags ]
Specifies default topology scheduling options for the queue.
-extsched options on the bsub command are merged with
DEFAULT_EXTSCHED options, and
-extsched options override any conflicting
queue-level options set by DEFAULT_EXTSCHED.
For example, if
DEFAULT_EXTSCHED=RMS[RMS_SNODE;rails=2] and a job is
submitted with
-extsched "RMS[base=hostA;rails=1;ptile=2]", LSF uses
the following resulting options for scheduling:
RMS_SNODE;rails=1;base=hostA;ptile=2
DEFAULT_EXTSCHED can be used in combination with
MANDATORY_EXTSCHED in the same queue. For example:
-extsched "RMS[base=hostA;ptile=2]"
DEFAULT_EXTSCHED=RMS[rails=2]
MANDATORY_EXTSCHED=RMS[RMS_SNODE;ptile=4]
LSF uses the resulting options for scheduling:
RMS_SNODE;rails=2;base=hostA;ptile=4