[Webkit-unassigned] [Bug 84885] [Resource Timing] Implement buffer limits

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri May 25 10:08:08 PDT 2012


https://bugs.webkit.org/show_bug.cgi?id=84885





--- Comment #3 from Annie Sullivan <sullivan at chromium.org>  2012-05-25 10:07:12 PST ---
(In reply to comment #2)
> (In reply to comment #1)
> > I think we need to choose a smaller initial number. I know the spec says 150, but I think the spec is wrong. We can always change it later if it turns out we're wrong.
> > 
> > I'd be fine with the default buffer size being 0 or being something small enough to give time for the first script to run (e.g. 5-10). 
> > 
> > We shouldn't be wasting memory on every page for this when a incredibly tiny percentage of pages will actually use this API.
> 
> That's fine with me. I wouldn't totally discount its use though. Every analytics tool will use this data. We put the buffer in, at their request, so that they could continue to load their script after load fires and still have access to the site's data. I'd imagine a significant percentage of sites use analytics.

To add some stats, 46% of the Quantcast top million sites are currently using Analytics: http://trends.builtwith.com/analytics/Google-Analytics

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list