New issue
Advanced search Search tips

Issue 838092 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

3.2%-7.2% regression in speedometer at 554012:554349

Project Member Reported by jarin@google.com, Apr 30 2018

Issue description

Hi Jakob, could this be caused by "Reland "[builtins] Introduce further constant & external reference indirections"?
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Apr 30 2018

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

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


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

android-nexus5
android-webview-nexus6
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-win7-gpu-intel
win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 30 2018

Cc: mstarzinger@chromium.org jgruber@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14ae6003c40000

Reland "[builtins] Introduce further constant & external reference indirections" by jgruber@chromium.org
https://chromium.googlesource.com/v8/v8/+/3f99a376ddfc1a724f94d55b4a39986e56cd33b2

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Mergedinto: 838041
Status: Duplicate (was: Assigned)

Sign in to add a comment