https://github.com/mozilla/energia
INACTIVE - http://mzl.la/ghe-archive - Desktop Browser Power benchmarking Utility
https://github.com/mozilla/energia
inactive unmaintained
Last synced: 4 months ago
JSON representation
INACTIVE - http://mzl.la/ghe-archive - Desktop Browser Power benchmarking Utility
- Host: GitHub
- URL: https://github.com/mozilla/energia
- Owner: mozilla
- Archived: true
- Created: 2013-12-09T13:46:56.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2019-03-28T04:22:19.000Z (about 6 years ago)
- Last Synced: 2024-09-19T02:27:00.995Z (8 months ago)
- Topics: inactive, unmaintained
- Language: JavaScript
- Homepage:
- Size: 217 KB
- Stars: 9
- Watchers: 4
- Forks: 4
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# energia
Desktop Browser Power benchmarking Utility
## Dependencies
* Intel's Power Gadget, Intel's BLA (Win only)
* Python 3 with numpy, pandas & pyzmq
* ZeroMQ
Note that on Windows the WinPython distribution comes with all dependencies required.
## Idle benchmark on Windows, OSX and Linux
The idle benchmark collects CPU & GPU statistics of the requested browsers idling on predefined pages.
The set of browsers and pages to benchmark can be specified in a json configuration file.
The collected metrics are aggregated from several tools which can also be specified in the configuration file, currently *energia* supports *PowerGadget* and *BLA*.
*PowerGadget* is the only tool available on all platforms. Finally, the aggregated results are stored in a csv file.
```bash
python3 benchmark.py -c config.json
```
The command will collect data about the idle usage of the browsers and the websites specified in the configuration file and produce a csv file.
## Distributed execution
The benchmark supports distributed execution through a simple dispatcher-worker architecture.
To run the benchmark on a cluster, issue on each worker the following command:
```bash
python3 benchmark.py --is_worker -a 192.168.0.1 # the address has to point to your dispatcher node
```
Finally launch the dispatcher process on a different node:
```bash
python3 benchmark.py --is_dispatcher ...
```
Note that the dispatcher and the workers can be started in any order at any time.
The dispatcher's configuration will then be propagated to all slaves automatically and the websites
partioned evenly among all of them. Once the execution is complete, a csv file is generated on the dispatcher node.