New issue
Advanced search Search tips

Issue 840693 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.9%-4% regression in speedometer2 at 555679:555708

Project Member Reported by bmeurer@google.com, May 8 2018

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=840693

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


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

chromium-rel-win7-gpu-intel
Cc: haraken@chromium.org mlippautz@chromium.org mstarzinger@chromium.org jgruber@chromium.org
Owner: mlippautz@chromium.org
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/12f704dbc40000

[builtins] Update isolate-independent list & related fixups by jgruber@chromium.org
https://chromium.googlesource.com/v8/v8/+/519bd47f6c9a48dfe551fd23f37d4bd52a4992a7

[oilpan] Enable incremental marking buildflag by mlippautz@chromium.org
https://chromium.googlesource.com/chromium/src/+/bd9ac13acc9d99a4f192b2734613545c187a319c

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Reverted because both changes affect the benchmark. Lets wait for the reland.
Status: WontFix (was: Assigned)

Sign in to add a comment