New issue
Advanced search Search tips

Issue 622565 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

HostResolver should support more fine grained priority for speculative requests

Project Member Reported by csharrison@chromium.org, Jun 23 2016

Issue description

The net predictor keeps a DNS queue apart from the one maintained by HostResolver that does two interesting things:

1. Congestion control. If requests are waiting in the queue for too long we just clear the queue.
2. Throttling. We only allow 3 requests at a time into the HostResolver's queue.

These features should be implemented lower in the stack so that a separate queue is not necessary for the predictor to maintain.


 
I have some thoughts how it could be done.
So, what about calling content::PreresolveUrl with |motivation| passed to HostResolver? The resolver will have another path for preresolve requests, which would be stored in the same sort of queue as predictor has.
Owner: ----
Owner: mge...@chromium.org

Comment 4 by mge...@chromium.org, Mar 23 2018

Owner: ----
Status: Available (was: Assigned)

Sign in to add a comment