New issue
Advanced search Search tips

Issue 889042 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

1%-2.2% regression in system_health.memory_mobile at 592773:592809

Project Member Reported by lanwei@chromium.org, Sep 25

Issue description

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

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


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

Android Nexus5X WebView Perf
Android Nexus6 WebView Perf

system_health.memory_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

memory.top_10_mobile - Benchmark documentation link:
  None
Cc: thakis@chromium.org
Owner: thakis@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16453234e40000

Reland "Roll clang 340925:342523." by thakis@chromium.org
https://chromium.googlesource.com/chromium/src/+/bbb140b822e8ae819be4fae81c2c7e713a7a5e8e
1.189e+08 → 1.205e+08 (+1.615e+06)

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

Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Mergedinto: 889062
Status: Duplicate (was: Assigned)

Sign in to add a comment