New issue
Advanced search Search tips

Issue 612805 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Need scroll start versions of key scroll latency breakdown metrics

Project Member Reported by tdres...@chromium.org, May 18 2016

Issue description

When one of our end-to-end scroll latency metrics regresses, we need to figure out which part of the pipeline regressed. We can do this for scroll updates, but not for scroll start. We should add ScrollStart versions of all of these metrics.

Event.Latency.TouchToHandled_{Main,Impl}
-> Event.Latency.ScrollStart.TouchToHandled_{Main,Impl}

Event.Latency.ScrollUpdate.HandledToRendererSwap_{Main, Impl}
-> Event.Latency.ScrollStart.HandledToRendererSwap_{Main, Impl}

Event.Latency.ScrollUpdate.RendererSwapToBrowserNotified
-> Event.Latency.ScrollStart.RendererSwapToBrowserNotified

Event.Latency.ScrollUpdate.BrowserNotifiedToBeforeGpuSwap
-> Event.Latency.ScrollStart.BrowserNotifiedToBeforeGpuSwap

Event.Latency.ScrollUpdate.GPUSwap
-> Event.Latency.ScrollStart.GPUSwap
 
Cc: skyos...@chromium.org
Sami - I'm hoping this will make it easier to track down regressions like the scroll latency ones we're getting stumped by.
Good idea!
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 9 2016

Labels: -M-53 M-54 MovedFrom-53
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment