New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 828188 link

Starred by 1 user
Status: Assigned
Owner:
nzolghadr@chromium.org
Cc:
tdres...@chromium.org
skare@chromium.org
isherman@chromium.org
asvitk...@chromium.org
█ rkaplow@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 640921



Sign in to add a comment

Many Event.Latency.QueueingTime.* histograms are unmapped and using substantial storage/bandwidth

Project Member Reported by wittman@chromium.org, Apr 2 2018 
The following Event.Latency.QueueingTime histograms are not declared in histograms.xml, and combined are in the 99th percentile for size.

Event.Latency.QueueingTime.GestureScrollBeginDefaultAllowed
Event.Latency.QueueingTime.GestureScrollBeginDefaultPrevented
Event.Latency.QueueingTime.GestureScrollUpdateDefaultAllowed
Event.Latency.QueueingTime.GestureScrollUpdateDefaultPrevented
Event.Latency.QueueingTime.MouseDownDefaultPrevented
Event.Latency.QueueingTime.MouseLeaveDefaultAllowed
Event.Latency.QueueingTime.MouseLeaveDefaultPrevented
Event.Latency.QueueingTime.MouseMoveDefaultAllowed
Event.Latency.QueueingTime.MouseMoveDefaultPrevented
Event.Latency.QueueingTime.MouseUpDefaultPrevented
Event.Latency.QueueingTime.MouseWheelDefaultAllowed
Event.Latency.QueueingTime.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=b140562cdcac6b2f7d34c95b0a1d43e6add0fd83&l=200

If these are not needed, please update the logic to exclude their recording. Otherwise please add them to histograms.xml.

Comment 1 by tdres...@chromium.org, Apr 3 2018

Cc: tdres...@chromium.org
Owner: nzolghadr@chromium.org
Same as crbug.com/828189.

Comment 2 by wittman@chromium.org, May 18 2018

Blocking: 640921

Comment 3 by asvitk...@chromium.org, Oct 16 

Hi,

Could the histograms in question be cleaned up?

Given that they're unmapped they've likely never been used at all in the dashboards and are just wasting resources on user's machines.

Ideally, we could just remove their code. Another option if removing the code is too much work right now is to add definitions for them in histograms.xml and mark them expired, so that they're no longer logged.
►

Sign in to add a comment