benchmark_harness

Can you elaborate on your claim that Dart designers optimized Delta Blue when porting it to Dart? Here's the Dart code for Delta Blue: https://github.com/dart-lang/benchmark_harness/blob/master/e... Here's the JavaScript code for Delta Blue: https://code.google.com/p/v8/source/browse/branches/bleeding... I see a JS class for Constraint, and a Dart class for Constraint. I see a JS class for Strength, and a Dart class for Strength. This goes on and on. In fact, I see a top-level function for chainTest() in both JavaScript and Dart.

[disclaimer: I work on the Dart team] I talked to our VM engineers, and they mentioned that the Benchmarks Game does not perform a warm-up before it runs the benchmark. This affects the Dart performance, because the Dart VM does not yet have on-stack replacement (OSR). Both Java and V8 have OSR so they perform better in the Benchmarks Game. If you look at Dart's benchmark harness, https://github.com/dart-lang/benchmark_harness, you'll see that we perform a small warm up before we start measuring. It would be cool if Benchmarks Game did a warmup, too. We plan to implement OSR but it's not there yet.

Digging through some of the links, here are the sources I found: The JavaScript version is part of the Octane Web Benchmark. The DeltaBlue component is here: https://code.google.com/p/octane-benchmark/source/browse/lat... The Dart version of DeltaBlue is here: https://github.com/dart-lang/benchmark_harness/blob/master/e...