New issue
Advanced search Search tips

Issue 818251 link

Starred by 1 user
Status: WontFix
Owner:
yigu@chromium.org
Closed: Mar 2018
Cc:
flackr@chromium.org
jbroman@chromium.org
mustaq@chromium.org
yigu@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.6%-852% regression in smoothness.top_25_smooth at 539762:539910

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

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

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

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


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

chromium-rel-mac11-air
chromium-rel-mac12
chromium-rel-win7-dual
chromium-rel-win7-x64-dual
Project Member

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

Cc: flackr@chromium.org yigu@chromium.org jbroman@chromium.org
Owner: yigu@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14ebfb0c440000

Disable runtime feature CompositeOpaqueFixedPosition by yigu@chromium.org
https://chromium.googlesource.com/chromium/src/+/5770b54a09c563cf56d7d2aaf7cdda80c59e1be1

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

Comment 4 by yigu@chromium.org, Mar 2 2018 

 Issue 818247  has been merged into this issue.

Comment 5 by yigu@chromium.org, Mar 5 2018

Status: WontFix (was: Assigned)
The suspected patch disabled a runtime feature CompositeOpaqueFixedPosition so that certain scrolls would fall back to main thread which caused the regression. It's expected because roughly the same amount of improvement was found when the feature was enabled.
►

Sign in to add a comment