Automatically bind LSF daemons to specific CPU cores

Bind a defined set of LSF daemons to CPU cores to distribute CPU resources among critical functions and improve scheduling performance.

You can bind LSF daemons to specific CPU cores by setting the LSF_INTELLIGENT_CPU_BIND parameter to Y in the lsf.conf file.

LSF binds LSF daemons to CPU cores according to the CPU binding configuration file for that host. If a CPU binding file does not exist for the host, LIM automatically detects the topology of that host and binds the LSF daemons according to the automatic binding policy.

LSF initially detects the topology of each management host and management candidate, binds the LSF daemons according to the automatic binding policy, and generates a CPU binding configuration file for that host. These configuration files are in the LSF_ENVDIR/cpu_binding directory and the file names are in the format of host_name.cluster_name and are in the LSF_ENVDIR/cpu_binding directory. LSF binds LSF daemons to CPU cores according to this CPU binding configuration file.

If the CPU binding configuration file no longer exists for the host, LIM automatically detects the topology of that host again and binds the LSF daemons according to the automatic binding policy.

If the CPU binding configuration file is changed, you must restart the LSF daemons by running the following commands in the following order to apply the new CPU binding settings:
  1. bctrld restart lim
  2. bctrld restart sbd
  3. badmin mbdrestart
Note: CPU binding configuration files do not support comments. LSF removes any comments in the CPU binding configuration files after LIM restarts.

The LSF_INTELLIGENT_CPU_BIND parameter takes precedence over other CPU binding parameters. If you enable LSF_INTELLIGENT_CPU_BIND, LSF ignores the following parameters:

  • EGO_DAEMONS_CPUS
  • ESTIMATOR_CPUS
  • LSF_DAEMONS_CPUS
  • MBD_QUERY_CPUS
Note: Because this feature binds LSF daemons to eight CPU cores, the LSF_INTELLIGENT_CPU_BIND parameter is ignored if the management and management candidate hosts have fewer than eight CPU cores.