ironic maybe, but when the difference between the best and worst performers over the entire benchmark is 3 frames at 60fps, it isn't unreasonable to think of su

ironic maybe, but when the difference between the best and worst performers over the entire benchmark is 3 frames at 60fps, it isn't unreasonable to think of sunspider as indicative of not much any more. as js engine improvements are starting to level off, the tradeoffs that have to be made become more complex. optimizing for one case can cause a regression in another (just take a look at the heuristics used for when tracing should kick in for trace-/jaegermonkey). at some point, insisting on monotonically decreasing times for a test that takes a quarter of a second becomes pretty much akin to the megahertz or megapixel races.