Enabling processor binding for LSF job processes

About this task

LSF supports the following binding options for sequential jobs and parallel jobs that run on a single host:

  • BALANCE
  • PACK
  • ANY
  • USER
  • USER_CPU_LIST
  • NONE

Procedure

Enable processor binding cluster-wide or in an application profile.

  • Cluster-wide configuration (lsf.conf)

    Define LSF_BIND_JOB in lsf.conf to enable processor binding for all execution hosts in the cluster. On the execution hosts that support this feature, job processes are hard bound to selected processors.

  • Application profile configuration (lsb.applications)

    Define BIND_JOB in an application profile configuration in lsb.applications to enable processor binding for all jobs that are submitted to the application profile. On the execution hosts that support this feature, job processes are hard bound to selected processors.

If BIND_JOB is not set in an application profile in lsb.applications, the value of LSF_BIND_JOB in lsf.conf takes effect. The BIND_JOB parameter that is configured in an application profile overrides the lsf.conf setting.

Note: BIND_JOB and LSF_BIND_JOB are deprecated in LSF Standard Edition and LSF Advanced Edition. You should enable LSF CPU and memory affinity scheduling in with the AFFINITY parameter in lsb.hosts. If both BIND_JOB and affinity scheduling are enabled, affinity scheduling takes effect, and BIND_JOB is disabled. If both LSF_BIND_JOB and affinity scheduling are enabled, affinity scheduling takes effect, and LSF_BIND_JOB is disabled. BIND_JOB and LSF_BIND_JOB are the only affinity options available in LSF Express Edition.