New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 887485 link

Starred by 1 user
Status: WontFix
Owner:
sunn...@chromium.org
Closed: Sep 21
Cc:
sunn...@chromium.org
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

11% regression in blink_perf.image_decoder at 591216:591291

Project Member Reported by alexclarke@chromium.org, Sep 20 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 20 

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

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


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

Win 7 Nvidia GPU Perf

blink_perf.image_decoder - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 21

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

Revert "cc: Finish frame early if main thread is idle regardless of redraw state" by sunnyps@chromium.org
https://chromium.googlesource.com/chromium/src/+/2bbe289cc8e1ba48e6aac024521bafeb489f3ea0
1322 → 1476 (+154.1)

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

Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

Comment 4 by sunn...@chromium.org, Sep 21

Status: WontFix (was: Assigned)
Due to a revert
►

Sign in to add a comment