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

Issue 833285 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.4%-77.5% regression in rasterize_and_record_micro.top_25 at 550524:550616

Project Member Reported by toyoshim@chromium.org, Apr 16 2018

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

android-nexus5X
android-nexus7v2
android-one
android-webview-nexus6
chromium-rel-win7-gpu-intel
Project Member

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

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

Roll AFDO from 67.0.3395.0_rc-r1 to 67.0.3396.0_rc-r1 by afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/443f4880b248dd6ade32463d8e383e3c01bba289

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Owner: g...@chromium.org
Status: Fixed (was: Assigned)
gbiv: Sorry this perf regression bug didn't cc you when the CL landed, the bug for autorolls has since been fixed.

It also looks like this regression was fixed with the AFDO roll to 68.0.3398.0_rc-r1, so marking this bug fixed.

Sign in to add a comment