NEW111016
All ports should implement ResourceHandle::didChangePriority() 
https://bugs.webkit.org/show_bug.cgi?id=111016
Summary All ports should implement ResourceHandle::didChangePriority()
James Simonsen
Reported 2013-02-27 14:59:57 PST
During page load, we can improve Speed Index scores by ~3% if images requested normally are prioritized over images that are preloaded. In order to do that properly, we need to lower the priority of preloaded resources, then have a way to increase it once the resource is normally requested. This mechanism is ResourceHandle::didChangePriority(), but it needs to be implemented on all platforms before we can rely on it.
Attachments
Add attachment proposed patch, testcase, etc.
Brady Eidson
Comment 1 2013-02-27 20:38:30 PST
I'd really like it if we started thinking about things like this at the resource loader level or the memorycache/cachedresource level. Implementing this at ResourceHandle: A - Is not compatible with all platform's networking layers B - Will just require piping through more communication up from ResourceHandle to ResourceLoader or CachedResoure
James Simonsen
Comment 2 2013-02-28 16:08:02 PST
We should definitely enforce the priorities in WebCore too. However, there are still further queues in the network layer, notably for DNS and TCP connections. We need some way of ensuring those queues stay ordered too. I don't think it's a bad thing if all ports aren't able to implement that, but the ones that can should. That's why I filed the bug.
Brady Eidson
Comment 3 2013-02-28 16:16:07 PST
(In reply to comment #2) > We should definitely enforce the priorities in WebCore too. However, there are still further queues in the network layer, notably for DNS and TCP connections. We need some way of ensuring those queues stay ordered too. I don't think it's a bad thing if all ports aren't able to implement that, but the ones that can should. That's why I filed the bug. 1 - All ports *can* benefit from additional prioritization at the ResourceLoader/MemoryCache/CachedResource level 2 - Implementing this at that level does not preclude piping the notification *downwards* towards ResourceHandle for those ports that can benefit there.
Note You need to log in before you can comment on or make changes to this bug.