Startup.FirstCommitNavigationTime2 has too many buckets and lots of data in the overflow bucket. |
||
Issue descriptionStartup.FirstCommitNavigationTime2 has too many buckets and lots of data in the overflow bucket. Looks like the histogram is defined to have 250 buckets, which is way more than needed: https://uma.googleplex.com/histograms/?endDate=20161123&dayCount=1&histograms=Startup.FirstCommitNavigationTime2&fixupData=true&showMax=true&filters=isofficial%2Ceq%2CTrue&implicitFilters=isofficial For example, there's 1ms granularity for the first 40 or so buckets. This is wasteful of UMA storage space and memory use. Additionally, the histogram still seems to have a lot of data in the overflow bucket - so seems like the max value for the histogram (1 minute) is not sufficient. I suggest cleaning up this histogram to: a) Reducing the buckets to a more typical 50 b) Setting a higher maximum - e.g. 10 minutes
,
Dec 15 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2102529172119d82b237672850732c22d4037ae6 commit 2102529172119d82b237672850732c22d4037ae6 Author: wnwen <wnwen@chromium.org> Date: Thu Dec 15 18:00:58 2016 Android: Clean up histogram buckets range Startup.FirstCommitNavigationTime2 BUG= 668726 Review-Url: https://codereview.chromium.org/2559823004 Cr-Commit-Position: refs/heads/master@{#438872} [modify] https://crrev.com/2102529172119d82b237672850732c22d4037ae6/chrome/android/java/src/org/chromium/chrome/browser/tab/TabWebContentsObserver.java [modify] https://crrev.com/2102529172119d82b237672850732c22d4037ae6/tools/metrics/histograms/histograms.xml
,
Dec 15 2016
|
||
►
Sign in to add a comment |
||
Comment 1 by pasko@chromium.org
, Dec 9 2016