New issue
Advanced search Search tips

Issue 840774 link

Starred by 1 user
Status: WontFix
Owner:
khushals...@chromium.org
Closed: May 2018
Cc:
piman@chromium.org
khushals...@chromium.org
primiano@google.com
chrishtr@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

8.2%-90.1% regression in thread_times.simple_mobile_sites at 556041:556269

Project Member Reported by primiano@google.com, May 8 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, May 8 2018 

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

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


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

android-nexus5
android-nexus5X
android-one
android-webview-nexus5X
android-webview-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 9 2018

Cc: chrishtr@chromium.org piman@chromium.org khushals...@chromium.org
Owner: khushals...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11d5037bc40000

cc: Enable checkerimaging only on developer opt-in. by khushalsagar@chromium.org
https://chromium.googlesource.com/chromium/src/+/465219a86327b393fb6d92e894fd80919f9f9a0a

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

Comment 4 by khushals...@chromium.org, May 9 2018

Status: WontFix (was: Assigned)
There is no regression, decode work moved from background worker thread to raster threads since we don't async decode by default anymore.

https://chromeperf.appspot.com/report?sid=a939054141fb1482b28fd30e9b4a7edffaca398ea245eea5a2c749ebc08d45da
►

Sign in to add a comment