DataUse.MessageSize.AllServices.* histograms are confusing |
||
Issue descriptionDataUse.MessageSize.AllServices.* histograms are sparse histograms, and each bucket in the histogram corresponds to a specific service. The histogram would be more readable if it was an enumerated or a linear histogram. Sparse histograms have disadvantages: (i) chrome://histograms does not show COUNT or AVERAGE for them. (ii) The buckets are not labeled, which makes the histogram difficult to read. I think a better approach is followed by Memory.PressureLevel histogram which uses STATIC_HISTOGRAM_POINTER_BLOCK macro to record multiple counts for the same bucket which makes the histogram more readable.
,
Nov 17 2016
New histograms need to be created as per this approach, and old histograms need to be obsoleted. I will follow this approach for new histograms.
,
Jan 6 2017
STATIC_HISTOGRAM_POINTER_BLOCK macros use 32 bit counter. If the counter overflows, the UMA will not be reported. So sparse histograms seem to be the viable option. http://crbug.com/679046
,
Nov 2 2017
Raj, what's the status?
,
Nov 3 2017
Ping?
,
Dec 20 2017
Any updates here?
,
Feb 7 2018
Refreshed during triage.
,
Mar 27 2018
Refreshed during triage.
,
May 18 2018
Closing this since there is no plan to move from sparse histogram. |
||
►
Sign in to add a comment |
||
Comment 1 by bengr@chromium.org
, Oct 28 2016Status: Assigned (was: Untriaged)