DNS pre-resolver in net/ should be disabled for HTTP resources when data saver is enabled |
|||||||||
Issue descriptionCurrently, the DNS pre-resolver in net/predictor.cc triggers pre-resolution of hostnames. The pre-resolution happens while the page is loading, and helps speed up connecting to the web servers when a resource is fetched later during the pageload. However, for users that have data saver enabled, the HTTP resources are fetched via data saver proxy, and so there is no need for pre-resolving the hostnames that correspond to the HTTP resources. DNS pre-resolver for HTTP resources should be disabled for users that have data saver on. This would help in reducing the bytes on the wire.
,
Feb 13 2017
What about the less common case where the resource can't be served via proxy, e.g., when the proxy issues a bypass message? I think this is probably a good idea, but we should run an experiment to be sure.
,
Feb 13 2017
Yes, this should be done via the experiment.
,
Nov 2 2017
,
Dec 14 2017
,
Dec 21 2017
,
Feb 7 2018
Refreshed during triage.
,
Feb 7 2018
If somebody wants to take it over, here is the CL to start with: https://chromium-review.googlesource.com/c/chromium/src/+/828051
,
Mar 26 2018
Refreshed during triage.
,
Jun 22 2018
,
Jun 22 2018
,
Aug 8
Refreshed during triage.
,
Sep 24
,
Oct 23
Archiving since I have no plans of doing it in the near future. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by tbansal@chromium.org
, Jan 9 2017Status: Untriaged (was: Assigned)