New issue
Advanced search Search tips

Issue 841883 link

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



Sign in to add a comment

1.4% regression in loading.desktop at 556089:556222

Project Member Reported by majidvp@chromium.org, May 10 2018 
A small regression.
Project Member

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

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

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


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

chromium-rel-win7-gpu-intel
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 10 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/103007d7c40000

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 17 2018

Status: WontFix (was: Assigned)
Its a 1%(5ms) regression on TheOnion. I thought may be its some image that we were async decoding by default earlier but not anymore, since it became opt-in only, but that's not the case. Still this looks noise, since decode scheduling is the only thing that patch changed.
►

Sign in to add a comment