New issue
Advanced search Search tips

Issue 820085 link

Starred by 1 user
Status: Duplicate
Owner:
jgruber@chromium.org
Closed: Mar 2018
Cc:
machenb...@chromium.org
yangguo@chromium.org
jgruber@chromium.org
hablich@chromium.org
tebbi@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.1%-5.6% regression in speedometer at 540801:540925

Project Member Reported by tebbi@chromium.org, Mar 8 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Mar 8 2018 

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

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


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

chromium-rel-win7-gpu-ati
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 9 2018

Cc: machenb...@chromium.org jgruber@chromium.org yangguo@chromium.org hablich@chromium.org
Owner: jgruber@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14d75bca440000

[builtins] Enable embedded builtins and add testing variants by jgruber@chromium.org
https://chromium.googlesource.com/v8/v8/+/abcc28ced071faee637d5fd59d06cfdf80d8ea3f

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 4 by jgruber@chromium.org, Mar 9 2018

Mergedinto: 819121
Status: Duplicate (was: Assigned)
►

Sign in to add a comment