New issue
Advanced search Search tips

Issue 817829 link

Starred by 1 user
Status: Duplicate
Merged: issue 817826
Owner:
dtapu...@chromium.org
Closed: Mar 2018
Cc:
boliu@chromium.org
dtapu...@chromium.org
mustaq@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.7%-28.3% regression in thread_times.key_mobile_sites_smooth at 539608:539707

Project Member Reported by mustaq@chromium.org, Mar 1 2018 
Seems there are quite a few other matrices that have improved...
Project Member

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

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

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


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

android-webview-nexus5X
android-webview-nexus6
Project Member

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

Cc: dtapu...@chromium.org boliu@chromium.org
Owner: dtapu...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1480e424440000

Reland "Enable mojo based synchronous compositor" by dtapuska@chromium.org
https://chromium.googlesource.com/chromium/src/+/837639b937d3d1a084c246258ad1f460e4f0f68e

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

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

Mergedinto: 817826
Status: Duplicate (was: Assigned)
Overall thread times improved. This change moves work off the IO thread over to the compositor thread how mojo works.
►

Sign in to add a comment