New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 844583 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

19% regression in blink_perf.layout at 558153:558156

Project Member Reported by npm@chromium.org, May 18 2018

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, May 18 2018

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

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


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

android-nexus5
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 19 2018

Cc: afdo-chr...@skia-buildbots.google.com.iam.gserviceaccount.com
Owner: g...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1296f0e4240000

Roll AFDO from 68.0.3428.0_rc-r1 to 68.0.3429.0_rc-r1 by afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/fcb575c8904446db7b5a84c93bf45cf06c5b50a8

Assigning to sheriff gbiv@chromium.org because "Roll AFDO from 68.0.3428.0_rc-r1 to 68.0.3429.0_rc-r1" is a roll.

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

Comment 4 by g...@chromium.org, May 22 2018

Ack; thanks. Will look into this along with issue 844584, since I'm seeing a similar (though less common) "AFDO roll happened, so the perf gets to change drastically, too" thing here.

Sign in to add a comment