New issue
Advanced search Search tips

Issue 914795 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.7% regression in system_health.memory_mobile at 613930:613951

Project Member Reported by petermarshall@chromium.org, Dec 13

Issue description

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

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


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

Android Nexus6 WebView Perf

system_health.memory_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks
Cc: jarin@chromium.org
Owner: jarin@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/13e7e0ae140000

Revert "[constant-tracking] Track constants by default." by jarin@chromium.org
https://chromium.googlesource.com/v8/v8/+/8abde08a7cce1314faae56fe214f0a11bbcb546b
memory:webview:all_processes:reported_by_chrome:v8:effective_size: 7.655e+06 → 7.822e+06 (+1.666e+05)

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

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

Sign in to add a comment