Issue metadata
Sign in to add a comment
|
11.1%-19% regression in rendering.desktop/queueing_durations at 603845:603866 |
||||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 8
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1124b875e40000
,
Nov 8
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/1124b875e40000
,
Nov 9
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1775ee07e40000
,
Nov 9
Looks like a regression but it's noisy.
,
Nov 9
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/1775ee07e40000 Reland "Enable Perfetto by default for all telemetry tests" by oysteine@chromium.org https://chromium.googlesource.com/chromium/src/+/3bb24369bef996b43b2d2711f0033ba472f779ea queueing_durations: 0.1803 → 0.2116 (+0.03127) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Nov 13
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 8