Issue metadata
Sign in to add a comment
|
10.1% regression in blink_perf.bindings at 568607:568711 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 27 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12909433240000
,
Jun 28 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/12909433240000 [embedded-builtins] Enable on all arches except x86 for benchmarks by sigurds@chromium.org https://chromium.googlesource.com/v8/v8/+/f5a8352b0fbba0d88104de7949a0d0c238765cf8 64 → 58.04 (-5.96) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Jul 10
This is an expected regression of a change that significantly improves memory consumption per-tab: https://bugs.chromium.org/p/chromium/issues/detail?id=856027#c7 We are in the process of addressing the performance regressions the CL introduced. One CL we committed to this end is: https://chromium.googlesource.com/v8/v8/+/23dbb81d8f434cd79858cb3562386bca19cc0d36
,
Jul 10
,
Jul 17
,
Jul 24
This has been reverted for M69
,
Oct 16
This is a micro-benchmark, and we won't be fixing this. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jun 27 2018