Dromaeo

The Dromaeo JavaScript Performance Test Suite. Named after the Dromaeosaurs - or 'fast lizard'.

How to Use It

Dromaeo: http://dromaeo.com/

Visiting the main Dromaeo page you are given a collection of tests which can be run. Generally these tests are designed to be more "real world" in nature (testing a number of features simultaneously). Each test should have a full description explaining what the test is achieving along with an indication of what is being tested.

If you don't wish to run all of the available tests, and only run a sub-section of them, you can filter tests via the URL, like so:

• http://dromaeo.com/?array (this will only run array-related tests)
• http://dromaeo.com/?regexp (this will only run RegExp-related tests)

You have full regular expression support so something like the following will work, as well:

• http://dromaeo.com/?(array|regexp) (only run RegExp or Array-related tests)

Running the Tests

To begin you can run the tests by simply hitting the 'Run' button. It should be capable of running in Firefox 2+, Safari 3+, Opera 9+, and Internet Explorer 6+. Please report any problems that you may have.

You can pause/resume the tests at any time, using the 'Pause' button (it won't affect the final numbers).

Viewing the Results

After the tests have finished running you'll be presented with a full breakdown of the tests (including sub-tests). Each individual sub-test will have its mean value presented in conjunction with an error spread of the results.

Additionally, you'll be given a URL for your results, saved on the server, which you can refer back to at any point, like the following:

• http://dromaeo.com/?id=190 (A single Firefox run.)

Once you've received a URL (and associated unique ID) for your test results you can then use it to compare against other result sets , like so:

• http://dromaeo.com/?id=188,189,190 (Compares three WebKit, Opera, and Firefox runs.)

Methodology

There are a number of techniques that the Dromaeo suite uses in order to achieve accurate results. Together they provide a solid foundation for allowing significant performance analysis to be completed.

Versioning

All tests have an automatic version number, meaning that when the contents of a test change its results will no longer be used for comparison against other mis-matched results. This is taken care of, automatically, by the suite. For example, if you run the the test "3D Mesh Transformation v115" and then (at some point later, after changes run "3D Mesh Transformation v116" - and try to compare the results - no comparison will be allowed.

This is especially important as it allows for a tangible upgrade process to exist, for tests, considering that bugs or adjustments will inevitably arise causing some amount of conflict to occur. With this being completely baked into the process

Saved Results

All test results are automatically saved to the

Statistical Confidence

• Statistical confidence
• Error

Script Speed vs. Rendering Speed

• sss