Understanding RQL normalization between Platform LSF and EGO

Mapping slots in a way that considers both threads and cores affects RQL normalization (a part of the load-level computation) across hosts in a cluster. Because the computed load-level may be artificially lowered, RQL normalization never considers threads. By default, however, RQL normalization does not consider the number of cores, either. This default behavior can be changed.

Interacting with related LSF parameters

If your cluster is running the Platform LSF application manager on EGO, there are parameters that interact with and/or duplicate the functionality of EGO_DEFINE_NCPUS:
  • LSF_ENABLE_DUALCORE: If set to "cores," this parameter is equivalent to EGO_DEFINE_NCPUS. They both define how ncpus is computed.

    If EGO_DEFINE_NCPUS is set to...

    Then RQL normalization considers...

    procs

    processors

    cores

    processors and cores

    threads

    processors and cores, but not threads

    Note:

    In cases where both EGO and LSF parameters provide definitions, the EGO parameter takes precedence.

  • LSF_RQL_CONSIDER_DUALCORE: This parameter instructs the lim to consider the number of cores when computing the RQL normalization. It is set in conjunction with LSF_ENABLE_DUALCORE. Note the following interactions:

    • If both LSF_ENABLE_DUALCORE and LSF_RQL_CONSIDER_DUALCORE are set, then RQL normalization takes into account both cores on a machine with dual-core processors.

    • If LSF_RQL_CONSIDER_DUALCORE is set, but LSF_ENABLE_DUALCORE is not, then LSF_RQL_CONSIDER_DUALCORE is ignored.

    • If EGO_DEFINE_NCPUS is set, then LSF_RQL_CONSIDER_DUALCORE option is always ignored. (RQL normalization always considers foremost how ncpus is defined by the EGO cluster administrator.)