LSF Version 7.3 - Platform LSF Configuration Reference

If your cluster runs a large amount of blocking mode (bsub -K) and interactive jobs (bsub
-I), response to batch queries can become very slow. If you run large number of bsub -I or
bsub -K jobs, you can define the threads to the number of processors on the master host.
Default
Not defined
LSB_PSET_BIND_DEFAULT
Syntax
LSB_PSET_BIND_DEFAULT=y | Y
Description
If set, Platform LSF HPC binds a job that is not explicitly associated with an HP-UX pset to
the default pset 0. If LSB_PSET_BIND_DEFAULT is not set, LSF HPC must still attach the
job to a pset, and so binds the job to the same pset used by the LSF HPC daemons.
Use LSB_PSET_BIND_DEFAULT to improve LSF daemon performance by automatically
unbinding a job with no pset options from the pset used by the LSF daemons, and binding it
to the default pset.
Default
Not defined
LSB_QUERY_PORT
Syntax
LSB_QUERY_PORT=port_number
Description
Optional. Applies only to UNIX platforms that support thread programming.
This parameter is recommended for busy clusters with many jobs and frequent query requests
to increase mbatchd performance when you use the bjobs command.
This may indirectly increase overall mbatchd performance.
The port_number is the TCP/IP port number to be used by mbatchd to only service query
requests from the LSF system. mbatchd checks the query port during initialization.
If LSB_QUERY_PORT is not defined:
•
mbatchd uses the port specified by LSB_MBD_PORT in lsf.conf, or, if
LSB_MBD_PORT is not defined, looks into the system services database for port numbers
to communicate with other hosts in the cluster.
•
For each query request it receives, mbatchd forks one child mbatchd to service the request.
Each child mbatchd processes one request and then exits.
If LSB_QUERY_PORT is defined:
•
mbatchd prepares this port for connection.The default behavior of mbatchd changes, a
child mbatchd is forked, and the child mbatchd creates threads to process requests.
lsf.conf
426 Platform LSF Configuration Reference