This project is now deprecated, please consider the latest version of PowerAPI available from here.
PowerAPI is a scala-based library for monitoring energy at the process-level. It is based on a modular and asynchronous event-driven architecture using the Akka library.
PowerAPI differs from existing energy process-level monitoring tool in its pure software, fully customizable and modular aspect which let user to precisely define what he wants to monitor, without any external device.
PowerAPI offers an API which can be used to express request about energy spent by a process, following its hardware resource utilization (in term of CPU, memory, disk, network, etc.).
PowerAPI is completely written in Scala (v. 2.9.1+), using the Akka library (v 2.0.1+). Configuration part is managed by the Typesafe Config (integrated version from the Akka library). PowerAPI project is fully managed by Maven (v. 3).
There are two ways to acquire PowerAPI: With or without Maven repositories. In other words, directly from Maven repositories (to get stable or snapshot versions), or from our Git repository (to get the source code).
Stable versions are available from the Maven central repository. Thus, you just have to put on your pom.xml file your desired modules. That's all.
Snapshot versions are available from the OSS Sonatype repository. Thus, you have to add this following repository location:
<repository>
<id>OSS Sonatype snapshot repository</id>
<url>https://oss.sonatype.org/content/repositories/snapshots</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>After that, you just have to put on your pom.xml file your desired modules.
Without Maven repositories, you have to deal with our Git repository as explain bellow:
To acquire PowerAPI, simply clone it via your Git client:
git clone git://github.com/abourdon/powerapi-akka.gitAs PowerAPI is a Maven managed project, you have to launch the install command at the root directory (here, powerapi_akka_directory) in order to compile and install it to your local machine:
cd $powerapi_akka_directory
mvn installBy default, all modules are selected to be installed. Be careful to correctly selecting yours, depending on your environment and the use case you want to do (see pom.xml file at the root directory for more details).
For Eclipse IDE users, make sure you have installed both:
- the Eclipse Scala IDE plugin, depending on your Eclipse version ;
- the m2eclipse-scala plugin at the following update site URL: http://alchim31.free.fr/m2e-scala/update-site. More information can be find on this post.
In the way you acquire PowerAPI from Maven repositories, you can directly use it as a Jar project in your pom.xml file.
In the way you acquire PowerAPI from our Git repository, you can navigate to your desired module and use it as a standard Maven module:
cd $powerapi_akka_directory/sensors/sensor-cpu-api
mvn testAs said above, configuration part is managed by the Typesafe Config. Thus, be aware to properly configure each module from its .conf file(s).
Let's take an example for the fr.inria.powerapi.formula.formula-cpu-dvfs module, which implements the PowerAPI CPU Formula using the well-known formula, P = c * f * V * V, where c constant, f a frequency and V its associated voltage.
To compute this formula, fr.inria.powerapi.formula.formula-cpu-dvfs module has to know:
- the CPU Thermal Design Power value;
- the array of frequency/voltage used by the CPU.
This information can be written in its associated configuration file as the following:
powerapi {
cpu {
tdp = 105
frequencies = [
{ value = 1800002, voltage = 1.31 }
{ value = 2100002, voltage = 1.41 }
{ value = 2400003, voltage = 1.5 }
]
}
}
Each module can have its own configuration part. See more details in its associated README file.
PowerAPI is based on a modular and asynchronous event-driven architecture using the Akka library. Architecture is centralized around a common event bus where each module can publish/subscribe to sending events. One particularity of this architecture is that each module is in passive state and reacts to events sent by the common event bus.
These modules are organized as follow:
As its name indicates, Core module gather all kernel functionnalities that will be used by other modules. More particulary, this module defines the whole types used by PowerAPI to define its architecture.
This module also defines the essential Clock class, responsible of the periodically sending of the Tick message, later responsible of the process of the PowerAPI business part.
To compute energy spent by a process through its hardware resource utilization, PowerAPI cuts computation in two parts:
- Hardware resource process utilization monitoring;
- Computation of the energy implies by the hardware resource process utilization.
Sensor modules or Sensors represents a set of Sensor, responsible of the monitoring of hardware resource process utilization. Thus, there is a CPU Sensor, a memory Sensor, a disk Sensor and so on.
As information is given by operating system, there is one Sensor implementation by operating system type. Thus there is a CPU Linux Sensor, a CPU Windows Sensor, and so on.
Set of Formula, responsible of the computation of the energy spent by a process on a particular hardware resource (e.g CPU, memory, disk, network), following information provided by its associated Sensor.
A Formula may depend on the type of the monitored hardware resource. Thus, for the same hardware resource, several Formula implementations could exist.
Set of Processor, which listen to Formula events sending by the common event bus in order to process them before their display by Reporters. Thus Processor can be, for example, an aggregating process unit, aggregating messages sent by Formula module to be more meaningful during the display by a given Reporter.
Set of Reporter, which listen to Processor events in order to display them to the final user. Thus, a Reporter is just a graphical representation of the PowerAPI request to the final user, which can be displayed for example into a console, a file or a graph.
The Library module defines the API that can be used by user to interact with PowerAPI.
Process-level energy monitoring is based on a periodically computation that can be expressed via the API. Here there are several examples to describe PowerAPI's API:
What is the CPU energy spent by the 123 process? Please give me fresh results every 500 milliseconds
Assume that process run under Linux, using a procfs file system on a standard CPU architecture.
Thus, we need to use the procfs CPU Sensor implementation and a given CPU Formula implementation, let's say the DVFS version. Add to this the desire to display CPU energy spent by process into a console. So we need to:
- Activate the desired modules:
Array(
classOf[fr.inria.powerapi.sensor.cpu.proc.times.CpuSensor],
classOf[fr.inria.powerapi.formula.cpu.dvfs.CpuFormula]
).foreach(PowerAPI.startEnergyModule(_))- Ask to PowerAPI to provide the CPU energy spent by the 123 process, every 500 milliseconds, using a console Reporter and aggregating results by timestamp produced every 500 milliseconds:
PowerAPI.startMonitoring(
process = Process(123),
duration = 500 milliseconds,
processor = classOf[fr.inria.powerapi.processor.TimestampAggregator],
listener = classOf[fr.inria.powerapi.reporter.ConsoleReporter],
)Note that we use listener as parameter instead of reporter for legacy reasons.
Based on the previous code, we simply have to add a new Reporter which will be able to display CPU energy information into a chart.
PowerAPI integrates a Reporter using the JFreeChart Java graph library. So let's add it to the PowerAPI system:
PowerAPI.startMonitoring(
listener = classOf[fr.inria.powerapi.reporter.JFreeChartReporter]
)That's all!
We are working on new energy modules (Sensor + Formula) development. If you are interested to participate, feel free to contact us via our GitHub webpage or mail us at [email protected]!
Copyright (C) 2013 Inria, University Lille 1.
PowerAPI is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
PowerAPI is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.
You should have received a copy of the GNU Affero General Public License along with PowerAPI. If not, see http://www.gnu.org/licenses/.