mozilla / energia

INACTIVE - http://mzl.la/ghe-archive - Desktop Browser Power benchmarking Utility

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.

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:

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:

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.

energia's Issues

CODE_OF_CONDUCT.md file missing

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please reach out to [email protected].

(Message COC001)