[webkit-dev] setTimeout as browser speed throttle
mike at belshe.com
Tue Sep 30 23:32:26 PDT 2008
Thanks everyone for the feedback and ideas. Sounds like we're converging.
Maciej - I'll volunteer to do the work in the webkit tree to reduce the
existing timer and testing that is deemed necessary (actually, I think this
is mostly a testing task; the code change is trivial). I think the test I
sent earlier (timers2) gives a decent indication of how much cpu various
timer minimums will drain. Of course, this completely depends on the
hardware you are running on; but I could imagine taking that test on a very
low end box and using that for basic data.
Also - I have run tests in general web browsing to see sites affected by the
timer clamp (I just added a counter to count every time it kicks in). I
reran this tonight; even gmail triggers it occassionally. But overall it is
rarely triggered. I think this is to be expected since applications that
exist today are built on the technology which they have available to them,
and this feature didn't exist before on any major browser. A year after we
deploy this, maybe we'll start to see some apps use it. :-)
On Tue, Sep 30, 2008 at 10:36 PM, Darin Fisher <darin at chromium.org> wrote:
> On Tue, Sep 30, 2008 at 7:14 PM, Maciej Stachowiak <mjs at apple.com> wrote:
>> 2) Consider making WebKit's default minimum timer limit lower - something
>>> like 3ms-5ms. I don't know what we would do to verify that this is "safe
>>> enough" or who would do the work. Maybe Hyatt?
> We are in the process of verifying this now ;-) Our eyes and ears are open
> (have been) for bug reports related to this. Right now, we are happy to be
> trying something radical. In the absence of problem reports, when do we
> declare success?
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev