Define ncpus—processors, cores, or threads

An EGO cluster administrator must define how ncpus is computed. Usually, the number of available EGO slots is equal to the value of ncpus; however, slots can be redefined at the resource group level. The ncpus definition is globally applied across the cluster.

  1. Open ego.conf.
    • Linux: $EGO_CONFDIR/kernel/conf/ego.conf

    • Windows: %EGO_CONFDIR%\kernel\conf\ego.conf

  2. Define the parameter EGO_DEFINE_NCPUS=[procs | cores | threads].
    Set it to one of the following:
    • procs (where ncpus=procs)

    • cores (where ncpus=procs *cores)

    • threads (where ncpus=procs *cores * threads)

    By default, ncpus is set to procs (number of processors).

    Note:

    In clusters with older lim daemons/services that do not recognize cores and threads, this parameter is ignored. In clusters where only the master lim recognizes cores and threads, the master lim assigns defaults values (for example, in Platform LSF 6.2: 1 core, -1 thread).

  3. Save and close ego.conf.
Note:

As a best practice, set EGO_DEFINE_NCPUS instead of EGO_ENABLE_DUALCORE. The functionality of EGO_ENABLE_DUALCORE=y is preserved by setting EGO_DEFINE_NCPUS=cores.

Interacting with related LSF parameters

If your cluster is running the Platform LSF application manager on EGO, there is a duplicate parameter in lsf.conf called LSF_ENABLE_DUALCORE. In the case where both EGO and LSF parameters provide a definition for ncpus, the EGO parameter takes precedence.