Add UMA metric to measure time spend in finding closest matching layer during hit testing |
|||||
Issue descriptionThe logic to find the closest matching layer uses cached clips stored on the clip tree. This needs to change as the cached clips in the clip tree are being removed ( https://crbug.com/594675 ). Adding UMA metric will help us make sure there are no performance regressions because of the change
,
Feb 2 2017
,
Feb 2 2017
Your change meets the bar and is auto-approved for M57. Please go ahead and merge the CL to branch 2987 manually. Please contact milestone owner if you have questions. Owners: amineer@(clank), cmasso@(bling), ketakid@(cros), govind@(desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 3 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/665e887dd3515599663477e67012a4d4288c1d6f commit 665e887dd3515599663477e67012a4d4288c1d6f Author: Jayadev Dasika <jaydasika@google.com> Date: Fri Feb 03 20:09:57 2017 cc : Add UMA metric for finding closest matching layer to a point The logic to find the closest matching layer is going to change. Adding a UMA metric to track performance before and after the change. BUG= 685379 CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel Review-Url: https://codereview.chromium.org/2655853004 Cr-Commit-Position: refs/heads/master@{#447117} (cherry picked from commit ee0ab199b6e9bd10d179fa1cfb379eff943d8b9e) Review-Url: https://codereview.chromium.org/2672603007 . Cr-Commit-Position: refs/branch-heads/2987@{#298} Cr-Branched-From: ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943} [modify] https://crrev.com/665e887dd3515599663477e67012a4d4288c1d6f/cc/trees/layer_tree_impl.cc [modify] https://crrev.com/665e887dd3515599663477e67012a4d4288c1d6f/tools/metrics/histograms/histograms.xml
,
Feb 25 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by bugdroid1@chromium.org
, Jan 31 2017