[Webkit-unassigned] [Bug 81719] ResourceLoadScheduler casuses too much delay

[bugzilla-daemon at webkit.org]

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





--- Comment #2 from Gavin Peters <gavinp at chromium.org>  2012-03-21 08:23:25 PST ---
(In reply to comment #1)
> > Apparently the purpose of the ResourceLoadScheduler is to try to request JS and CSS in front of images, even if they're discovered out-of-order. Some buffering is needed to do this, but this is too much.
> 
> The code does know about the priority. Perhaps when the highest priority items are enqueued, the requests could be issued immediately?

Yes.  Embargoing to onload is too late.

The network stack itself should be able to deal with multiple requests coming in; the only problem is if you present high priority requests after low priority requests: an aggressive stack may potentially have requests already open.

So your proposed solution just embargoing the low priority requests until the highest priority requests have gone out should work, and make things much faster.


> 
> git annotate says japhet and antti are good people to consult about how this should work.

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