AreWeFastYet

AreWeFastYet: tracking performance of popular JavaScript engines

• The x-axis is the date we ran tests, and the y-axis is the score of the benchmark.
• The front page displays a hybrid of historical data, as well as the most recent samples.
• You can click on a datapoint to see a tooltip with more information.
• Tooltips will either give you the revision range used to condense a point, or the changelog that occurred in between two points.
• Tooltips can be dragged around, for easier comparison.
• Some benchmarks use time (lower is better), and some use points (higher is better). We orient all graphs so lower is better, visually.
• Use the "machine" menu to see different computers' benchmark results.
• Use the "Breakdown" menu to drill down into individual benchmarks.
• You can click and highlight any area of any graph to zoom in. It might pause to download data.
• You can unzoom by double-clicking inside a graph.
• A graph will refresh every 5 minutes if it is not zoomed in and has no attached tooltips.

• Who maintains this site?

  This site is maintained by Mozilla's JavaScript team.

• How does it work?

  AWFY is automated. Throughout the day, we checkout the latest source code to each available JavaScript engine, and compile it. Then we run it through some benchmark suites, and tally up the scores into a database. This data gets exported as JSON which can then be easily plotted.

• Why is Opera not available?

  Historically AWFY runs standalone, command-line JavaScript shells - not the web browsers that embed them. Opera doesn't provide a standalone shell. Currently we have some machines that also runs browser versions, but now Opera has switched to V8 (js engine of Chrome). As a result it doesn't seems that important to include a seperate line, since you can mostly look to the v8 line.

• Why is IE not available?

  AWFY runs cutting-edge not released yet versions of the browsers to track improvements and regressions as they happen. The browsers get tested multiple times a day, since that is how fast performance can change from one to another build. IE doesn't provide nightly builds. So a new build is only available every few months/years. In that regard it doesn't really make sense to run benchmarks on it every few hours. (This is nexto the fact that currently only one machine would be able to run IE versions and that IE builds are quite invasive and touch a lot of the machine OS upon install and might cause unrelated regressions on other browsers). Maybe the release of Spartan will bring us closer on having IE on AWFY.

• Why is Safari not tested on 32-bit machine?

  Safari defaults to 64-bit machines and doesn't need to worry about 32-bit anymore. Big pieces of their engine is 64-bit only. As a result showing Safari on 32-bit machines would give incorrect results.

• What are the graphs?

  The top left-hand graph is Mozilla's Kraken benchmark. The top right-hand graph is Apple's SunSpider benchmark. The bottom graph is Google's V8 benchmark suite.

• What do the hover tips mean?

  "Source" is where we got the engine from. "Tested" is when we downloaded the engine, compiled, and tested it. "Rev" is the unique point in the engine's revision history we tested. If the datapoint represents a range, there may be multiple revs. These numbers/strings are for developers to see which changes happened in between points in the graph.

• What's ARM?

  ARM is the CPU present in many embedded devices, like smartphones. We're interested in this for mobile Firefox and Firefox OS.

• Is this open source?

  Fo' sho', https://github.com/haytjes/arewefastyet

• Suggestions?

  e-mail