Skip to content
GitLab

Architecture · Changes

Page history
Wiki EAR4.3 authored by Oriol Vidal's avatar Oriol Vidal
Show whitespace changes
Inline Side-by-side
Architecture.md
View page @ 7ff3e622
[[_TOC_]] [[_TOC_]]
# EARD: Node Manager ## EARD: Node Manager
EAR's daemon is a per-node process that provides privileged metrics of each node as well as a periodic power monitoring service. Said periodic power metrics are sent to EAR's database either directly or via the database daemon (see the [configuration page](Configuration)). EAR's daemon is a per-node process that provides privileged metrics of each node as well as a periodic power monitoring service. Said periodic power metrics are sent to EAR's database either directly or via the database daemon (see the [configuration page](Configuration)).
For more information, see [EARD](EARD). For more information, see [EARD](EARD).
# EARDBD: Database Manager ## EARDBD: Database Manager
The database daemon acts as an intermediate layer between any EAR component that inserts data and the EAR's database, in order to prevent the database server from collapsing due to getting overrun with connections and insert queries. The database daemon acts as an intermediate layer between any EAR component that inserts data and the EAR's database, in order to prevent the database server from collapsing due to getting overrun with connections and insert queries.
For more information, see [EARDBD](EARDBD). For more information, see [EARDBD](EARDBD).
# EARGMD: Global Manager ## EARGMD: Global Manager
EAR's Global Manager Daemon (EARGMD) is a cluster wide component that controls the percentage of the maximum energy consumed. EAR's Global Manager Daemon (EARGMD) is a cluster wide component that controls the percentage of the maximum energy consumed.
For more information, see [EARGM](EARGM). For more information, see [EARGM](EARGM).
# EARL: The EAR Library ## EARL: The EAR Library
The EAR Library is the core of the EAR package. The EARL offers a lightweight and simple solution to select the optimal frequency for MPI applications at runtime, with multiple power policies each with a different approach to find said frequency. EARL uses the daemon to read performance metrics and to send application data to EAR's database. The EAR Library is the core of the EAR package. The EARL offers a lightweight and simple solution to select the optimal frequency for MPI applications at runtime, with multiple power policies each with a different approach to find said frequency. EARL uses the daemon to read performance metrics and to send application data to EAR's database.
For more information about the library itself, see [EARL](EARL). You can also read about [EAR policies](EARL#policies) and the [EAR API](EARL#ear-api) to use EAR as a third party library in you application. For more information about the library itself, see [EARL](EARL). You can also read about [EAR policies](EARL#policies) and the [EAR API](EARL#ear-api) to use EAR as a third party library in you application.
# EARLo: EAR Loader ## EARLo: EAR Loader
The EAR Loader is the responsible for loading the EAR Library. The EAR Loader is the responsible for loading the EAR Library.
It is a small and lightweight library loaded by the [EAR SLURM Plugin](#ear-slurm-plugin) that identifies the user application and loads its corresponding EAR Library distribution. It is a small and lightweight library loaded by the [EAR SLURM Plugin](#ear-slurm-plugin) that identifies the user application and loads its corresponding EAR Library distribution.
For more information, see [EARLo](EAR Loader). For more information, see [EARLo](EAR Loader).
# EAR SLURM plugin ## EAR SLURM plugin
EAR SLURM plugin allows to dynamically load and configure the EAR library for the SLURM jobs, if the enabling argument is set or is enabled by default. Additionally, it reports any jobs that start or end to the nodes' EARDs for accounting and monitoring purposes. EAR SLURM plugin allows to dynamically load and configure the EAR library for the SLURM jobs, if the enabling argument is set or is enabled by default. Additionally, it reports any jobs that start or end to the nodes' EARDs for accounting and monitoring purposes.
......