On Dec 15, 2009, at 3:07 PM, Mike Belshe wrote:
On Tue, Dec 15, 2009 at 1:01 PM, Maciej Stachowiak <m...@apple.com>
wrote:
- what would you think of reducing the setTimeout(..., 500) to
something like setTimeout(..., 100)? This will cut the runtime of
the test by ~80% :-)
I don't know if you noticed in my comments below, but the gap
between individual tests is now 10ms, there is only a one-time
initial delay of 500ms to give browsers a chance to recover from the
effects of loading the driver page.
Ok - I had checked the code, saw the 500ms setTimeout there, and
then griped :-)
This sounds great!
OK cool. The 10ms between tests was necessary to address <https://bugs.webkit.org/show_bug.cgi?id=32505
>. It does increase variance a bit, but it's the only way to get rid
of the severe distortion from CPU stepping on modern Mac and Windows
systems. The new results should be much closer to what you get running
the command-line version.
Regards,
Maciej
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
