Issue metadata
Sign in to add a comment
|
57.7% regression in system_health.common_desktop at 545921:546051 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 29 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1616a4bb440000
,
Mar 31 2018
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/1616a4bb440000 Get navigation info without using FrameLoader snapshots by dproy@chromium.org https://chromium.googlesource.com/catapult/+/5d35a2c7122c1ac4a9a37e7743a19f628f25a38b [Telemetry] include story tags in benchmark_runner list by laszio@chromium.org https://chromium.googlesource.com/catapult/+/2943ee372877a1133027d036d6dc54232277bcc4 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Apr 3 2018
Assigning to dproy, it looks like your CL caused a larger regression and came first. Can you have a look?
,
Apr 11 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Mar 29 2018