Need scroll start versions of key scroll latency breakdown metrics |
||
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
,
May 18 2016
Good idea!
,
Jul 9 2016
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 |
||
Comment 1 by tdres...@chromium.org
, May 18 2016