diff options
| author | skyostil@google.com <skyostil@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-19 11:14:56 +0000 |
|---|---|---|
| committer | skyostil@google.com <skyostil@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-19 11:14:56 +0000 |
| commit | 3be8a36a7f83b58b4deff0dfbc51a74d5b9281e1 (patch) | |
| tree | 01724c75790c22204280cf8d5903e6429b072632 /tools/metrics | |
| parent | aba1eed20f314afba43c9f24283c4bd76f509323 (diff) | |
| download | chromium_src-3be8a36a7f83b58b4deff0dfbc51a74d5b9281e1.zip chromium_src-3be8a36a7f83b58b4deff0dfbc51a74d5b9281e1.tar.gz chromium_src-3be8a36a7f83b58b4deff0dfbc51a74d5b9281e1.tar.bz2 | |
Revert 207132 "Added UMA to track bytes for cacheable resources"
This change made a DCHECK fail in histogram.cc:94. This seems to be because the
maximum histogram value of base::TimeDelta::FromDays(30) overflows to
-1702967296, causing the condition at histogram.cc:237 to fail.
Build bot failure: https://chromegw.corp.google.com/i/clank.tot/builders/instrumentation-yakju-clankium-tot/builds/11465/steps/build/logs/stdio
> Added UMA to track bytes for cacheable resources
>
> This includes a count of received bytes with associated freshness
> lifetimes that are greater than 0, 4, and 24 hours, as well as
> counts of resource retrievals by freshness lifetime.
>
> BUG=249035
>
> Review URL: https://chromiumcodereview.appspot.com/16838005
TBR=bengr@chromium.org
Review URL: https://codereview.chromium.org/17274005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@207212 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/metrics')
| -rw-r--r-- | tools/metrics/histograms/histograms.xml | 28 |
1 files changed, 0 insertions, 28 deletions
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml index 1658339..454e7c7 100644 --- a/tools/metrics/histograms/histograms.xml +++ b/tools/metrics/histograms/histograms.xml @@ -4914,10 +4914,6 @@ other types of suffix sets. </summary> </histogram> -<histogram name="Net.HttpContentFreshnessLifetime" units="milliseconds"> - <summary>Length of time that a received resource will be cacheable.</summary> -</histogram> - <histogram name="Net.HttpContentLength" units="bytes"> <summary> Size of the response body. This is the actual number of bytes received, @@ -4926,30 +4922,6 @@ other types of suffix sets. </summary> </histogram> -<histogram name="Net.HttpContentLengthCacheable" units="bytes"> - <summary> - Size of the response body if it is cacheable. This is the actual number of - bytes received, which usually agrees with but is not necessarily the same as - the size specified by the Content-Length header. - </summary> -</histogram> - -<histogram name="Net.HttpContentLengthCacheable24Hours" units="bytes"> - <summary> - Size of the response body if it is cacheable for at least 24 hours. This is - the actual number of bytes received, which usually agrees with but is not - necessarily the same as the size specified by the Content-Length header. - </summary> -</histogram> - -<histogram name="Net.HttpContentLengthCacheable4Hours" units="bytes"> - <summary> - Size of the response body if it is cacheable for at least 4 hours. This is - the actual number of bytes received, which usually agrees with but is not - necessarily the same as the size specified by the Content-Length header. - </summary> -</histogram> - <histogram name="Net.HttpContentLengthDifference" units="bytes"> <summary> The difference between the size specified in the X-Original-Content-Length |