Issue metadata
Sign in to add a comment
|
23%-484% regression in performance_browser_tests at 603959:604040 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 6
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/111cedf5e40000
,
Nov 7
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/111cedf5e40000 Get performance_browser_tests working again. by miu@chromium.org https://chromium.googlesource.com/chromium/src/+/c9cee7e5db8b778279bf39c3a249ab1140616b83 CastV2Performance_gpu_60fps: 6.758 → 18.09 (+11.33) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Dec 17
Part of my change was fixing the timing/analysis logic. I believe the metric change is just due to fixing that. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 6