New issue
Advanced search Search tips

Issue 894121 link

Starred by 1 user
Status: WontFix
Owner:
rnk@google.com
Closed: Oct 22
Cc:
rnk@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7% regression in blink_perf.image_decoder at 597895:597927

Project Member Reported by m...@chromium.org, Oct 10 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 10 

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

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


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

Android Nexus6 WebView Perf

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

Comment 3 by m...@chromium.org, Oct 10

Cc: -m...@chromium.org
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Oct 11

Cc: rnk@google.com
Owner: rnk@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/15940ecae40000

Roll clang 343342:343880. by rnk@google.com
https://chromium.googlesource.com/chromium/src/+/4b0d30529e9fe28989bb37680bd6e26fae4546df
decode-gif: 4652 → 4931 (+278.9)

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

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

Comment 5 by rnk@google.com, Oct 22

Status: WontFix (was: Assigned)
We don't have the resources to bisect performance regressions caused by compiler updates, so I will close this as wontfix.
►

Sign in to add a comment