New issue
Advanced search Search tips

Issue 817826 link

Starred by 1 user
Status: WontFix
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

8.8%-30.8% regression in thread_times.key_silk_cases at 539608:539707

Project Member Reported by mustaq@chromium.org, Mar 1 2018 
See the link to graphs below.
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=817826

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


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

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

Comment 5 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/1622b8f0440000

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 6 by dtapu...@chromium.org, Mar 2 2018

Status: WontFix (was: Assigned)
The tasks are moved from the IO thread to the compositor thread with the mojo change. This is a benefit and expected change. CPU usage remains roughly the same.

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

 Issue 817829  has been merged into this issue.
Project Member

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

Status: Assigned (was: WontFix)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/119a4e38440000

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 9 by dtapu...@chromium.org, Mar 2 2018

Status: WontFix (was: Assigned)
Project Member

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

Status: Assigned (was: WontFix)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11936b24440000

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 11 by dtapu...@chromium.org, Mar 2 2018

Status: WontFix (was: Assigned)
►

Sign in to add a comment