On Jul 5, 2009, at 9:58 AM, Joe Mason wrote:
Maciej Stachowiak wrote:
I think the pauses were large in an attempt to get stable,
repeatable results, but are probably longer than necessary to
achieve this. I agree with you that the artifacts in "balanced"
power mode are a problem. Do you know what timer thresholds avoid
the effect? I think this would be a reasonable "1.0" kind of change.
Just a gut feeling, but I suspect the exact throttling algorithm
would vary too much from machine to machine and OS version to OS
version to ever find a good threshold to avoid it. The best thing
to do would be to have the harness turn off CPU throttling when it
starts. (This is possible from the commandline under Linux, and I
assume in Mac, but Windows might be a problem.)
The command line harness doesn't pause at all. It's the in-browser
harness is the one we are concerned about. We obviously can't turn off
CPU throttling from the JavaScript level. I'll see if I can still get
repeatable cross-browser results with a much smaller delay.
Regards,
Maciej
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
