Servo should have benchmarks in order to compare our performance against shipping browsers and to make sure our experiments lead in fruitful directions. These benchmarks should exercise enough features that they are not toy examples and should also exercise paths that are relevant to our research.

These are the things we want to measure, both for clock time and for parallelism.

• General layout performance
• DOM manipulation (JS -> Rust -> JS roundtrips)
• Memory usage
• of DOM
• of CSS selector matching

These are some benchmarks other browsers use. Perhaps some of these are reasonable for the above. Most benchmarks seem to be overly focused on JS engine performance.

• Kraken: can't find info on what this contains, but claims to be real workloads, so probably not exclusively JS
• GUIMark 2: graphics related tests
• BrowserMark: seems to test a wide variety of things
• canvas performance test
• WebVizBench: seems to test WebGL rendering
• HTML5 benchmark: mainly testing GC pauses during canvas operations
• CSS parsing microbenchmark
• CanvasMark
• WebGL Performance Benchmark
• renderperf3: WebGL benchmark
• Speedometer
• Maze - layout performance
• Web Tooling

• JetStream - seems to measure JS engine performance
• Octane: seems too focused on JS engine, but perhaps PDF.js benchmark is relevant due to it using canvas DOM APIs heavily
• RoboHornet: lots of DOM api benchmarks
• Dromaeo: specifically the DOM performance tests

• benchmark.js

• http://www.tomshardware.com/reviews/chrome-27-firefox-21-opera-next,3534.html
• http://trac.webkit.org/wiki/JavaScript%20and%20DOM%20Benchmarks
• https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/-R47hzmkdig