New issue
Advanced search Search tips

Issue 701769 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 692946
Owner:
Closed: Mar 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.1% regression in system_health.memory_mobile at 456663:456700

Project Member Reported by nzolghadr@chromium.org, Mar 15 2017

Issue description

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgtLWxtgsM


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

android-webview-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Mar 15 2017

Cc: verwa...@chromium.org
Owner: verwa...@chromium.org

=== Auto-CCing suspected CL author verwaest@chromium.org ===

Hi verwaest@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Toon Verwaest
  Commit : 4d2dd669676034a4b4135c069958051f259832de
  Date   : Tue Mar 14 09:11:11 2017
  Subject: [ic] Turn load-interceptor into a smi-handler

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/blank_about/blank_about_blank
  Change       : 1.06% | 2001486.66667 -> 2022788.0

Revision                           Result                  N
chromium@456662                    2001487 +- 15190.2      6       good
chromium@456681                    2009968 +- 0.0          6       good
chromium@456686                    2009968 +- 0.0          6       good
chromium@456689                    2009968 +- 0.0          6       good
chromium@456690                    2001648 +- 20379.8      6       good
chromium@456690,v8@f20261bfb4      2006364 +- 0.0          9       good
chromium@456690,v8@4d2dd66967      2020939 +- 15688.3      9       bad       <--
chromium@456690,v8@8e18765d69      2020411 +- 21786.9      14      bad
chromium@456690,v8@a5eec0ca0b      2020939 +- 15688.3      9       bad
chromium@456691                    2022788 +- 0.0          6       bad
chromium@456700                    2022788 +- 0.0          6       bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=blank.about.blank system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8985046522627963120

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5785532988129280


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Mergedinto: 692946
Status: Duplicate (was: Untriaged)

Sign in to add a comment