New issue
Advanced search Search tips

Issue 881456 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 7
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.2%-5.3% regression in blink_perf.image_decoder at 589034:589077

Project Member Reported by sullivan@chromium.org, Sep 6

Issue description

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

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


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

linux-perf

blink_perf.image_decoder - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
Cc: mcasas@chromium.org
Owner: mcasas@chromium.org
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/161dc20d640000

Do not use components/arc/common in non CrOs builds by mcasas@chromium.org
https://chromium.googlesource.com/chromium/src/+/e865a56bd15e1ff2acc8f6a0a919036c3f6760b8
823.2 → No values

Revert "Do not use components/arc/common in non CrOs builds" by mcasas@chromium.org
https://chromium.googlesource.com/chromium/src/+/34cd555a197d2296d99cf63d4d83b7297dc6a931
No values → 854

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

Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks
Status: WontFix (was: Assigned)
Pinpoint is showing the build broken/fixed, no regression found.

Sign in to add a comment