GitLab

They are complex to compute, and the results are basically there isn't any:
1) There is usually only one read ongoing (>99% of the time, except I
broke this bucket in M63...)
2) For writes, basically 90+% of the time we have only a single write to
   an entry, too. Most of the rest it's a second write following an
   optimistic write, which can't be easily parallelized since HttpCache writes
   with truncate = true. This isn't entirely impossible, though.

Bug: 757682
Change-Id: I7c65988e14a6d413b95122e9c7c39c922f77524f
Reviewed-on: https://chromium-review.googlesource.com/1122706Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Josh Karlin <jkarlin@chromium.org>
Commit-Queue: Maks Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575515}