New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 621554 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

Measure efficacy of speculative/predictive DNS resolutions

Project Member Reported by juliatut...@chromium.org, Jun 20 2016

Issue description

We should have a way to see how often DNS cache entries resolved by speculative or predictive DNS mechanisms are actually used later.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Aug 2 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7e8bf1c42475e7bf0cf31a0cbda952cb6cae5f99

commit 7e8bf1c42475e7bf0cf31a0cbda952cb6cae5f99
Author: juliatuttle <juliatuttle@chromium.org>
Date: Tue Aug 02 19:09:09 2016

DNS: Let requests specify a callback for future cache hits

To measure the effectiveness of various speculative DNS measures, allow
DNS requests to contain a cache hit callback that will be called every
time another request returns synchronously with cached data from the
same entry that the original request wrote or read.

To clarify, here's an example sequence of operations (assuming all
requests have callbacks set):

1. Request A resolves a name.
2. Request B resolves the same name while the result is still valid;
   the resolver calls request A's cache hit callback.
3. Request C resolves the same name again; the resolver calls the
   callbacks for both request A and B.
4. The cache is cleared on a network change.
5. Requests D and E both resolve the name. No callbacks are called,
   since there was no result cached for either request.
6. Request F resolves the name; the resolver calls the callbacks for
   requests D and E.

Notably, if multiple speculative resolutions occur, the cache hit
callbacks pile up, and future cache hits will call *all* of them.

BUG=621554

Review-Url: https://codereview.chromium.org/2083643003
Cr-Commit-Position: refs/heads/master@{#409262}

[modify] https://crrev.com/7e8bf1c42475e7bf0cf31a0cbda952cb6cae5f99/net/dns/host_cache.cc
[modify] https://crrev.com/7e8bf1c42475e7bf0cf31a0cbda952cb6cae5f99/net/dns/host_cache.h
[modify] https://crrev.com/7e8bf1c42475e7bf0cf31a0cbda952cb6cae5f99/net/dns/host_cache_unittest.cc
[modify] https://crrev.com/7e8bf1c42475e7bf0cf31a0cbda952cb6cae5f99/net/dns/host_resolver.cc
[modify] https://crrev.com/7e8bf1c42475e7bf0cf31a0cbda952cb6cae5f99/net/dns/host_resolver.h
[modify] https://crrev.com/7e8bf1c42475e7bf0cf31a0cbda952cb6cae5f99/net/dns/host_resolver_impl.cc
[modify] https://crrev.com/7e8bf1c42475e7bf0cf31a0cbda952cb6cae5f99/net/dns/host_resolver_impl.h
[modify] https://crrev.com/7e8bf1c42475e7bf0cf31a0cbda952cb6cae5f99/net/dns/host_resolver_impl_unittest.cc

Cc: -csharrison@chromium.org juliatut...@chromium.org
Owner: csharrison@chromium.org
Status: Assigned (was: Started)
csharrison, I'm passing this to you, since you're working on some of the speculative/predictive stuff right now.
Cc: alexilin@chromium.org csharrison@chromium.org
Owner: ----
Status: Available (was: Assigned)

Sign in to add a comment