New issue
Advanced search Search tips

Issue 887946 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Oct 3
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.5% regression in speedometer at 592765:592801

Project Member Reported by jarin@google.com, Sep 21

Issue description

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

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


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

android-nexus5x-perf

speedometer - Benchmark documentation link:
  None
Cc: thakis@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12f08197640000

Reland "Roll clang 340925:342523." by thakis@chromium.org
https://chromium.googlesource.com/chromium/src/+/bbb140b822e8ae819be4fae81c2c7e713a7a5e8e
2775 → 2895 (+119.7)

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

Benchmark documentation link:
  None
We temporarily disabled LTO on android in the roll, so this is probably expected and should recover when we turn it back on.
Owner: thakis@chromium.org
Cc: jarin@chromium.org
 Issue 887944  has been merged into this issue.
Mergedinto: 889062
Owner: ----
Status: Duplicate (was: Assigned)

Sign in to add a comment