JavaScript Perl C++ Mathematica C HTML Other
Latest commit 0f4b034 Feb 24, 2017 @h4writer committed on GitHub Merge pull request #116 from bnjbvr/wasm
Bump wasm benchmark version


AreWeFastYet is a set of tools used for benchmarking the major browser's JavaScript virtual machines against each other, as well as reporting the results on a website as insightful graphs showing the evolution of performance over time.

A public instance is hosted by Mozilla and running at



  1. Builder: A python driver ( that can create shell builds of spidermonkey/jsc/v8.
  2. Downloader: A python driver ( that can download browser builds of Firefox.
  3. Executor: ( is a python script that executes one or multiple benchmarks on one or more builds.


  1. Database: MySQL database that stores statistics.
  2. Collector: Hidden PHP script on the webserver, where stats get sent. (UPDATE.php in below diagram)
  3. Processor: Python aggregator that builds JSON data from the DB. ( in below diagram)
  4. Website: Static HTML as the frontpage, that queries JSON via XHR.
  5. Command center: Sends commands to the slaves on what to execute. (In construction.)

Components (2) and (4) must be on the same webserver, otherwise timestamps might not be computed correctly.

Keep in mind, most of this documentation is for posterity. AWFY was never intended to be a drag-and-drop all-in-one released product, so the procedures and scripts may be pretty rough.

System Diagram

Alt text

Benchmark locally

  1. Fetch the repo
  2. Create a (shell) or retrieve a (browser) build to benchmark

    • Creating a build:

      cd slave
      python -s mozilla
    • Pull a build:

      cd slave
  3. Benchmark

    python execute.p -b remote.octane -b remote.kraken



Put /server/awfy-server.config in /etc, and edit it to point at your database. Afterwards just run php migrate.php to create the tables and run the migrations. (Note: sometimes the database layout changes a bit. After pulling it is recommanded to run php migrate.php again. That will incremental adjust the database to the new layout, transforming existing entries.)

Data Collector

Drop website/UPDATE.PHP and website/internals.php somewhere, and rename UPDATE.PHP to something secret. Make sure you don't have directory listings enabled.

Slave DNS Config

Before running the benchmarks, add these lines to your /etc/hosts file and flush DNS cache. These host addresses are used by This configuration is needed for all the slaves that use the remote or local benchmarks. Only the shell benchmarks don't need it.

# Subdomains for AWFY   dromaeo.localhost   kraken.localhost   octane.localhost   massive.localhost   jetstream.localhost   speedometer.localhost   speedometer.localhost   sunspider.localhost   browsermark.local

Benchmark Computers

In development...

Data Processor

Put awfy-server.config in /etc, and edit it to point at your database and website/data folder. Then put in a cronjob. It will dump files where appropriate. does this every 15min. It is not safe to run two instance at once. A sample wrapper script is provided as generates various JSON files:

  1. "raw" and "metadata" files cache database queries from run to run, so we don't have to make expensive database queries.
  2. "aggregate" files are used for the front page.
  3. "condensed" files are used for one level of zooming, so users don't have to download the raw data set right away.

The metadata and raw JSON files are updated as needed. The aggregate and condensed files are always regenerated from the raw data.

There is also a script provided in the server folder. You can run this regularly to send e-mails for benchmarking machines that haven't sent results in a certain amount of time (this time is specified in awfy-server.config). It will send e-mail through the local SMTP server, using the "contact" field for each machine in the database. This field should be a comma-delimited list of e-mail addresses (i.e. ",").


Put the files somewhere. Currently php is needed for data.php, which pulls the data from the correct location. You just need to update config file (/etc/awfy-server.config) to refer the 'data' folder that contains the json/js files dumped by

Don't forget to replace the default machine number in website/awfy.js, which is the one that will show up in the first place. Note that AWFY's flot is slightly modified, so it might not work to just replace it with upstream flot.