| ... | ... | @@ -213,7 +213,7 @@ srun [...] my_app |
|
|
|
|
|
|
|
## Load Balancing
|
|
|
|
|
|
|
|
By default, EAR policies try to set the best CPU (and uncore, if [enabled](#controlling-uncore-infinity-fabric-frequency)) frequency according to node grain metrics.
|
|
|
|
By default, EAR policies try to set the best CPU (and uncore, if [enabled](#controlling-uncoreinfinity-fabric-frequency)) frequency according to node grain metrics.
|
|
|
|
This behaviour can be changed telling EAR to detect and deal with unbalanced workloads, i.e., there is no equity between processes regarding their MPI/computational activity.
|
|
|
|
|
|
|
|
When EAR detects such behaviour, policies slightly modify its way of CPU frequency selection
|
| ... | ... | @@ -258,7 +258,7 @@ For more information about Intel(R) SST, below are listed useful links to offici |
|
|
|
* [The Linux Kernel: Intel(R) Speed Select Technology User Guide](https://docs.kernel.org/admin-guide/pm/intel-speed-select.html)
|
|
|
|
|
|
|
|
EAR offers two environment variables that let to specify a list of priorities (CLOS) in two different ways.
|
|
|
|
The [first one](#EAR_PRIO_TASKS) will set a CLOS for each task involved in the job.
|
|
|
|
The [first one](#ear_prio_tasks) will set a CLOS for each task involved in the job.
|
|
|
|
On the other hand, the [second offered variable](#ear_prio_cpus) will set a list of priorities per CPU involved in the job.
|
|
|
|
Values must be within the range of available CLOS that Intel(R) SST provides you.
|
|
|
|
|
| ... | ... | @@ -369,7 +369,7 @@ Authorized users can modify this limit at submission time by using this environm |
|
|
|
|
|
|
|
## Disabling EAR's affinity masks usage
|
|
|
|
|
|
|
|
For both [Load Balancing](#load-balancing) and [Intel(R) SST](#support-for-intel-r-speed-select-technology)
|
|
|
|
For both [Load Balancing](#load-balancing) and [Intel(R) SST](#support-for-intelr-speed-select-technology)
|
|
|
|
support, EAR uses processes' affinity mask read at the beginning of the job.
|
|
|
|
If you are working on an application that changes (or may change) the affinty mask of tasks dynamically, this can lead some miss configuration not detected by EAR.
|
|
|
|
To avoid any unexpected problem, **we highly recommend you** to export `EARL_NO_AFFINITY_MASK` environment variable **even you are not planning to work with some of the mentioned features**.
|
| ... | ... | |