PageSize histograms have a minimum of 1000 KB |
||||||
Issue descriptionIf pages are less than 1000 KB, then they will be reported as 1000KB, skewing our results. Affected histograms: OfflinePages.BatchDelete.TotalPageSize OfflinePages.DeletePage.PageSize OfflinePages.PageSize
,
May 10 2016
,
May 11 2016
Could you make sure that we are not hitting some histogram resolution problems. Perhaps we should not be dividing by 1024 and that is how this is meant to work?
,
May 16 2016
This metric is recorded correctly, just the histogram is defined poorly for our purposes. We may need a custom counts histogram to get exactly the data we wand.
,
May 18 2016
Stealing from Jian
,
May 19 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/36d2aa2331eb458d324ac60b628abf721b8750f4 commit 36d2aa2331eb458d324ac60b628abf721b8750f4 Author: dimich <dimich@chromium.org> Date: Thu May 19 01:51:51 2016 Change UMA OfflinePages.PageSize to have better resolution in a typical range of offline page sizes. BUG= 610872 Review-Url: https://codereview.chromium.org/1989733002 Cr-Commit-Position: refs/heads/master@{#394634} [modify] https://crrev.com/36d2aa2331eb458d324ac60b628abf721b8750f4/components/offline_pages/offline_page_model.cc
,
May 23 2016
Does the metrics system support changing histogram buckets on the fly for a given metric?
,
Aug 29 2016
#7: Yes, in a sense that if a specific timeframe specified for a query, you get a new distribution after the new bits roll out. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dewittj@chromium.org
, May 10 2016