Many Event.Latency.BlockingTime.* histograms are unmapped and using substantial storage/bandwidth |
|||
Issue descriptionThe following Event.Latency.BlockingTime histograms are not declared in histograms.xml, and combined are in the 99th percentile for size. Event.Latency.BlockingTime.GestureScrollBeginDefaultAllowed Event.Latency.BlockingTime.GestureScrollBeginDefaultPrevented Event.Latency.BlockingTime.GestureScrollUpdateDefaultAllowed Event.Latency.BlockingTime.GestureScrollUpdateDefaultPrevented Event.Latency.BlockingTime.MouseDownDefaultPrevented Event.Latency.BlockingTime.MouseLeaveDefaultAllowed Event.Latency.BlockingTime.MouseLeaveDefaultPrevented Event.Latency.BlockingTime.MouseMoveDefaultAllowed Event.Latency.BlockingTime.MouseMoveDefaultPrevented Event.Latency.BlockingTime.MouseUpDefaultPrevented Event.Latency.BlockingTime.MouseWheelDefaultAllowed Event.Latency.BlockingTime.MouseWheelDefaultPrevented The histogram names are generated procedurally here: https://cs.chromium.org/chromium/src/content/browser/renderer_host/input/render_widget_host_latency_tracker.cc?rcl=565f5a3f82c45eb2a0da9d56696dbd5e00d8938b&l=216 If these are not needed, please update the logic to exclude their recording. Otherwise please add them to histograms.xml.
,
May 18 2018
Ping. Can we make a decision on what to do with these histograms and the ones in issue 828188, and take action? They're wasting substantial user bandwidth and UMA resources.
,
May 18 2018
,
May 22 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by tdres...@chromium.org
, Apr 3 2018Owner: nzolghadr@chromium.org