Track unread streams in SimpleCache.CheckCRCResult
commit7df11eb246bebb1c63682ebb1b8d9d14e28bf604
authorgavinp@chromium.org <gavinp@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Wed, 31 Jul 2013 03:04:28 +0000 (31 03:04 +0000)
committergavinp@chromium.org <gavinp@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Wed, 31 Jul 2013 03:04:28 +0000 (31 03:04 +0000)
tree4d230fe46145ce94eb4853508c9093553c0a358c
parent9f919cc7ed0db35c755a3b5add33fda6a44d4c1d
Track unread streams in SimpleCache.CheckCRCResult

We're seeing very high rates of reporting (~37%) of "Was never read to
end" from SimpleCache.CheckCRCResult. This is almost certainly from
unread metadata streams (~33% of streams) and HTTP payloads being
unread because the headers force an update (CantConditionalize = 4% of
requests, and Updated = 1% of requests).

By distinguishing never read streams from partially read streams, we
can be more sure about how often we risk providing bad data to
clients.

R=clamy,pasko
BUG=None

Review URL: https://chromiumcodereview.appspot.com/19749010

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214531 0039d316-1c4b-4281-b951-d872f2087c98
net/disk_cache/simple/simple_entry_impl.cc
net/disk_cache/simple/simple_entry_impl.h
tools/metrics/histograms/histograms.xml