3 ms·

http://arewefastyet.com/ http://arewefastyet.com/ still is being updated and has IonMonkey scores. V8 is still in the lead in 2 (out of 3) of the benchmark sui

• kevingadd 14y ago
  V8's "lead" on SunSpider is as much a fantasy as reality, since SunSpider performance is (IIRC) largely derived from how fast you can run setTimeout callbacks and not your actual JS performance. The tightly clustered scores on that graph make this pretty clear. On the other hand, it's pretty interesting to me that we're now in the state where SpiderMonkey wins at Kraken and v8 wins at v8bench. I wonder if there's some unconscious bias involved there, where each test suite contains cases the engine's developers care about the most, so they end up winning that test suite?
  • deleted 14y ago
    [deleted]
  • gsnedders 14y ago
    SunSpider hasn't (ever) relied on setTimeout performance (and AWFY runs everything through JS shells, and the standalone harness doesn't rely upon any callback-providing host objects). The closeness in performance is simply because it practically doesn't do anything that challenging to optimize — the biggest challenge is getting the compile time/execution time trade-off right. Kraken was developed fairly unrelated to SpiderMonkey, so I wouldn't say there's any deliberate bias there — V8 was explicitly optimized for the V8 benchmark suite as a deliberate aim, with several design decisions made to optimize for it, so it's advantage there is unsurprising.