New issue
Advanced search Search tips

Issue 880437 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

17.7% regression in blink_perf.image_decoder at 588049:588175

Project Member Reported by maxlg@chromium.org, Sep 4

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=880437

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


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

Win 7 Perf

blink_perf.image_decoder - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
Cc: ericrk@chromium.org
Owner: ericrk@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/171736c9640000

Re-land: Hold pre-decoded images until use or 250ms rather than 2 frames by ericrk@chromium.org
https://chromium.googlesource.com/chromium/src/+/dab7ed26d647862149d4c4b5e6d044fbe235571e
611 → 704 (+92.97)

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

Sign in to add a comment