New issue
Advanced search Search tips

Issue 792930 link

Starred by 3 users
Status: WontFix
Merged: issue 792921
Owner:
yigu@chromium.org
Closed: Dec 2017
Cc:
jochen@chromium.org
flackr@chromium.org
hichris...@gmail.com
machenb...@chromium.org
kinuko@chromium.org
drott@google.com
qyears...@chromium.org
npm@chromium.org
boliu@chromium.org
blink-w3c-test-autoroller@chromium.org
ericwilligers@chromium.org
yigu@chromium.org
petermarshall@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

23.2%-1024.7% regression in scheduler.tough_scheduling_cases at 521669:521790

Project Member Reported by npm@chromium.org, Dec 7 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 7 2017 

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

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


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

chromium-rel-mac11-air
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
linux-release
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 7 2017

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

Round the scroll offset synced back to main thread instead of flooring
By yigu@chromium.org · Tue Dec 05 15:49:54 2017
chromium @ a3ce2d3110a3f9177a41935daadd43ede72db553

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

Comment 4 by npm@chromium.org, Dec 7 2017

Mergedinto: 792921
Status: Duplicate (was: Assigned)

Comment 5 by yigu@chromium.org, Jan 10 2018

Status: WontFix (was: Duplicate)
Fix positioned elements were composited on high dpi devices (e.g. retina display) but not on low dpi ones to preserve lcd text. They are composited now with my patch so that the behavior on both devices is consistent.

The regression was detected on low dpi devices because of the newly composited elements. Meanwhile, the performance on high dpi devices didn't change (it's already "regressed" there). So this regression is "expected" because it matches the perf on high dpi devices. 

A new bug has been filed regarding the cause of the regression on both devices. See issue 800811.

Comment 6 by yigu@chromium.org, Jan 10 2018

Cc: serg...@chromium.org hichris...@gmail.com ericwilligers@chromium.org blink-w3c-test-autoroller@chromium.org qyears...@chromium.org jochen@chromium.org machenb...@chromium.org
 Issue 798424  has been merged into this issue.

Comment 7 by serg...@chromium.org, Jan 10 2018

Cc: -serg...@chromium.org

Comment 8 by yigu@chromium.org, Jan 26 2018

Cc: petermarshall@chromium.org drott@google.com
 Issue 792895  has been merged into this issue.
►

Sign in to add a comment