|
|
|
<img align="right" src="./images/logo.png">
|
|
|
|
Energy Aware Runtime (EAR) package provides an energy management framework for super computers.
|
|
|
|
EAR contains different components, all together provide three main services:
|
|
|
|
EAR 5.0 is a system software for energy management, accounting and optimization for super computers.
|
|
|
|
Main EAR services are:
|
|
|
|
|
|
|
|
1. An **easy-to-use** and **lightweight** optimization service to automatically
|
|
|
|
select the optimal CPU, memory and GPU frequency according to the application and the node characteristics.
|
|
|
|
This service is provided by two components: the EAR Library (EARL) and the EAR Node Manager (EARD).
|
|
|
|
EARL is a smart component which is loaded next to the application and offers
|
|
|
|
1. Application energy optimization. An **easy-to-use** and **lightweight** optimization service to automatically
|
|
|
|
select the optimal CPU, memory and GPU frequency according to the application and the node characteristics. This service is offered by EAR core components: The EAR library and EAR Node Manager.
|
|
|
|
EARL is a runtime library automatically loaded with the applications and it offers
|
|
|
|
application metrics monitoring and it can select the frequencies based on the
|
|
|
|
application behaviour on the fly.
|
|
|
|
The Library is loaded automatically through the EAR Loader (EARLO) and it can be easly integrated with different system batch schedulers (e.g., SLURM).
|
|
|
|
|
|
|
|
2. A complete **energy and performance accounting and monitoring system** mainly based
|
|
|
|
on relational SQL databases (MariaDB and PostgreSQL are currently supported).
|
|
|
|
The energy accounting system is configurable in terms of application details and
|
|
|
|
update frequency.
|
|
|
|
The EAR Database (EARDBD) is used to cache those metrics prior to DB insertions and optimize
|
|
|
|
the connectivity with the DB server.
|
|
|
|
Current EAR version already includes several report plugins for non-relational Databases such as EXAMON.
|
|
|
|
|
|
|
|
3. A **cluster energy manager** to monitor and control the energy consumed in
|
|
|
|
the system through the EAR Global Manager (EARGMD).
|
|
|
|
This control is configurable, it can dynamically adapt policy settings based on
|
|
|
|
global energy limits or just offer global cluster monitoring.
|
|
|
|
|
|
|
|
Visit the [architecture page](Architecture) for a detailed description of each
|
|
|
|
of these components.
|
|
|
|
The [user guide](User-guide) contains information about how to use EAR as an end
|
|
|
|
user in a production environment.
|
|
|
|
The [admin guide](Admin-guide) has all the information related to the installation
|
|
|
|
and setting up, as well as all core components details.
|
|
|
|
The Library is loaded automatically through the EAR Loader (EARLO) and it can be easly integrated with different system batch schedulers (e.g., SLURM). The EARL provides deep application accounting(both power/energy and performance) and energy optimization in a completelly transparent and dynamic way.
|
|
|
|
|
|
|
|
2. Job and Node monitoring: A complete **energy and performance accounting and monitoring system** .
|
|
|
|
Node and application monitoring are also provided by the EAR core components (EAR library and EAR node manager). These two components are the data provides and information is reported to the DB using the EAR DB manager (EARDBD).
|
|
|
|
The EARDBD is a distributed service offering buffering and aggregation of data, minimizing the number of connections with the DB server.
|
|
|
|
EAR includes several report plugins for both relational (MariaDB and PostgreSQL) and non-relational Databases such as EXAMON. EAR commands for data reporting are only based on relational DBs.
|
|
|
|
|
|
|
|
3. Cluster power management (powercap). A **cluster energy manager** to monitor and control the energy consumed in
|
|
|
|
the system through the EAR Global Manager (EARGMD) and EARD. EAR support a powerful and flexible configuration where different architectures with different power limits can be configured in the same cluster. CPU and CPU+GPU nodes are supported.
|
|
|
|
|
|
|
|
Visit the [architecture page](Architecture) for a detailed description of each of these components.
|
|
|
|
The [user guide](User-guide) contains information about how to use EAR as an end user in a production environment.
|
|
|
|
The [admin guide](Admin-guide) has all the information related to the installation and setting up, as well as all core components details.
|
|
|
|
|
|
|
|
## License
|
|
|
|
|
|
|
|
EAR is a open source software and it is licensed under both the BSD-3 license and EPL-1.0 license. Full text of both licenses can be found in COPYING.BSD and COPYING.EPL files.
|
|
|
|
EAR is a open source software and it is licensed under EPL-2.0 license.
|
|
|
|
Full text can be found in [COPYING.EPL-2.0](https://gitlab.bsc.es/ear_team/ear/-/blob/master/COPYING.EPL-2.0) file distributed with the source code.
|
|
|
|
|
|
|
|
Contact: [ear-support@bsc.es](mailto:ear-support@bsc.es)
|
|
|
|
|
| ... | ... | @@ -45,4 +37,4 @@ Contact: [ear-support@bsc.es](mailto:ear-support@bsc.es) |
|
|
|
[J. Corbalan, L. Alonso, C. Navarrete and C. Guillen, "Soft Cluster Powercap at SuperMUC-NG with EAR," 2022 IEEE 13th International Green and Sustainable Computing Conference (IGSC), Pittsburgh, PA, USA, 2022, pp. 1-8, doi: 10.1109/IGSC55832.2022.9969360](https://ieeexplore.ieee.org/document/9969360)
|
|
|
|
|
|
|
|
## Current version
|
|
|
|
This wiki corresponds to EAR version 4.3. |
|
|
\ No newline at end of file |
|
|
|
This wiki corresponds to EAR version 5.0. |
