New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 736270 link

Starred by 1 user
Status: Duplicate
Merged: issue 736262
Owner: ----
Closed: Jun 2017
Cc:
█ kraynov@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.7% regression in memory.top_10_mobile at 481722:481748

Project Member Reported by kraynov@chromium.org, Jun 23 2017 
See the link to graphs below.

Comment 1 by kraynov@chromium.org, Jun 23 2017 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=736270

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


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

android-webview-nexus6
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Jun 25 2017 


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: 429a81302fb5e00aba20e364db624c8eb110f881
  bad_revision : 5f2725f68003a78440a8c381b258bc338e910232

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/background/after_http_yandex_ru_touchsearch_text_science
  Change       : 3.05% | 87475106.6667 -> 90139725.3333

Revision             Result                   N
chromium@481721      87475107 +- 1122872      6      good
chromium@481725      89708109 +- 782177       6      bad
chromium@481728      90002168 +- 882994       6      bad
chromium@481735      90082552 +- 801185       6      bad
chromium@481748      90139725 +- 574525       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 memory.top_10_mobile

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

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


| 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!
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Jun 26 2017

Mergedinto: 736262
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : Marijn Kruisselbrink
  Commit : 5f2725f68003a78440a8c381b258bc338e910232
  Date   : Thu Jun 22 23:51:15 2017
  Subject: Change when leveldb wrappers are purged.

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/background/after_http_yandex_ru_touchsearch_text_science
  Change       : 2.18% | 87988642.6667 -> 89906765.3333

Revision             Result                   N
chromium@481721      87988643 +- 1332008      6      good
chromium@481723      88485283 +- 1189032      6      good
chromium@481724      88150435 +- 1484651      6      good
chromium@481725      90043469 +- 700734       6      bad       <--
chromium@481728      89931512 +- 849671       6      bad
chromium@481735      90130339 +- 714769       6      bad
chromium@481748      89906765 +- 831361       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 memory.top_10_mobile

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

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


| 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!
Project Member

Comment 10 by 42576172...@developer.gserviceaccount.com, Jun 27 2017 


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

Suspected Commit
  Author : Marijn Kruisselbrink
  Commit : 5f2725f68003a78440a8c381b258bc338e910232
  Date   : Thu Jun 22 23:51:15 2017
  Subject: Change when leveldb wrappers are purged.

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/background/after_http_yandex_ru_touchsearch_text_science
  Change       : 2.36% | 87850914.6667 -> 89926904.0

Revision             Result                   N
chromium@481721      87850915 +- 1232305      6      good
chromium@481723      88472824 +- 1285457      6      good
chromium@481724      88315981 +- 848849       6      good
chromium@481725      90223523 +- 305562       6      bad       <--
chromium@481728      89888163 +- 494452       6      bad
chromium@481735      89757773 +- 1022168      6      bad
chromium@481748      89926904 +- 913773       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 memory.top_10_mobile

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

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


| 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!
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Jun 27 2017 


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: 429a81302fb5e00aba20e364db624c8eb110f881
  bad_revision : 5f2725f68003a78440a8c381b258bc338e910232

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/foreground/http_yandex_ru_touchsearch_text_science
  Change       : 2.28% | 93908216.0 -> 96044792.0

Revision             Result                   N
chromium@481721      93908216 +- 1934450      6      good
chromium@481725      95538140 +- 1564082      9      bad
chromium@481728      95588088 +- 846419       6      bad
chromium@481735      95282424 +- 729342       6      bad
chromium@481748      96044792 +- 614420       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 memory.top_10_mobile

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

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


| 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!
►

Sign in to add a comment