New issue
Advanced search Search tips

Issue 874875 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Aug 16
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.8%-134.5% regression in rendering.mobile at 581987:582034

Project Member Reported by tdres...@chromium.org, Aug 16

Issue description

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

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


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

Android Nexus5X WebView Perf
Android Nexus6 WebView Perf
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/12ac5eea640000
Cc: r...@chromium.org
Owner: r...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/17aa7666640000

Revert "Roll clang 337439:338452." by rnk@chromium.org
https://chromium.googlesource.com/chromium/src/+/8457b638ed3550460518321e4a4a21b08c2e30f9
26.18 → 27.19 (+1.012)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: Fixed (was: Assigned)
The Clang roll was relanded in https://crrev.com/582951, so we've probably improved this benchmark again.

Sign in to add a comment