New issue
Advanced search Search tips

Issue 857083 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Oct 16
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocking:
issue v8:6666



Sign in to add a comment

10.1% regression in blink_perf.bindings at 568607:568711

Project Member Reported by nzolghadr@chromium.org, Jun 27 2018

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 27 2018

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=857083

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=5a33e670fe2fc3dfaeefb74beef1d3d55e14018c6312b21431f79ff41a55150c


Bot(s) for this bug's original alert(s):

android-one
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 28 2018

Cc: sigurds@chromium.org
Owner: sigurds@chromium.org
Status: Assigned (was: Untriaged)
📍 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
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







Cc: jgruber@chromium.org
Blocking: v8:6666
Labels: -M-69 M-70
This has been reverted for M69
Status: WontFix (was: Assigned)
This is a micro-benchmark, and we won't be fixing this.

Sign in to add a comment