New issue
Advanced search Search tips

Issue 604828 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Track the potential benefit of having events forced to be dispatched as passive events

Project Member Reported by dtapu...@chromium.org, Apr 19 2016

Issue description

Add a uma metric that tracks how much time was spent (aka saved) by dispatching an event forced passively.

Metric will be reported as "Event.PassiveListeners.ForcedNonBlockingLatency"
 
Status: Started (was: Assigned)
Project Member

Comment 2 by bugdroid1@chromium.org, Apr 22 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/cb268f1f0043f3426ba9f35282f50c2f16e3c185

commit cb268f1f0043f3426ba9f35282f50c2f16e3c185
Author: dtapuska <dtapuska@chromium.org>
Date: Fri Apr 22 18:08:48 2016

Add metric to determine the benefit of forcing an event listener to be passive.

Record the duration of processing an event when its dispatchType
was set to be forced non-blocking.

BUG= 604828 

Review URL: https://codereview.chromium.org/1907803002

Cr-Commit-Position: refs/heads/master@{#389163}

[modify] https://crrev.com/cb268f1f0043f3426ba9f35282f50c2f16e3c185/content/renderer/input/render_widget_input_handler.cc
[modify] https://crrev.com/cb268f1f0043f3426ba9f35282f50c2f16e3c185/tools/metrics/histograms/histograms.xml

Status: Fixed (was: Started)

Sign in to add a comment