Three Monkeys, Three Typewriters, Two Days

Comments: Performance testing pitfalls

Actually, looks like in SFX Dromeo *mostly* measures time spent in charAt, since you're getting 1000runs/s vs 1333runs/s without the harness. So the harness is just adding a 30% overhead.

But I agree, it seems like the Dromeo test harness is overly complex, IIRC we've had issues with it before.

Posted by Jonas Sicking at June 30, 2009 2:30 PM

Jonas, there's still js-execution overhead in SFX outside the harness; there's just a bit less than inside the harness. That is, the harness makes us fall off trace, but doesn't make SFX do the equivalent.

Posted by Boris at June 30, 2009 2:44 PM

SFX was renamed Nitro.
Now there's a Nitro Extreme branch in webkit svn.

Posted by RichB at June 30, 2009 3:17 PM

Nitro is just a marketing name for the engine:

http://www.nabble.com/Re%3A-Differences-between-Nitro-and-Squirrelfish.-p22211722.html

Posted by Kalle Vahlman at June 30, 2009 11:18 PM

It'd be nice to get this into 3.5.1.

Posted by Ian M at July 1, 2009 5:30 AM

Ian, I suspect the changes required to make this sort of closures-that-modify-things-they-close-over stuff to trace are going to be far too invasive to land in 3.5.x... I can't speak for the js team in terms of how they'll weigh the risk, though.

Posted by at July 1, 2009 10:47 AM
Post a comment