Issue metadata
Sign in to add a comment
|
48.7% regression in v8.browsing_mobile at 606112:607097 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 12
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12982253e40000
,
Nov 15
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/12982253e40000 Build internal android targets in telemetry_chrome_test. by jbudorick@chromium.org https://chromium.googlesource.com/chromium/src/+/e0c7bc0e869c70995d8b53d9a22e68294f07c7f2 v8-gc-scavenger: 22.69 → No values Revert "Build internal android targets in telemetry_chrome_test." by jbudorick@chromium.org https://chromium.googlesource.com/chromium/src/+/c7539ef6291836eff22077b38ae55bb62f536b99 v8-gc-scavenger: No values → 35.12 Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: None
,
Nov 15
Noise & build failures, nevermind |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 12