Issue 711299 link

Starred by 2 users

Issue metadata

Status:	Duplicate
Merged:	issue 711044
Owner:	----
Closed:	Apr 2017
Cc:	primiano@chromium.org
EstimatedDays:	----
NextAction:	----
OS:	----
Pri:	2
Type:	Bug-Regression
Performance-Sheriff M-59

1.5%-272.3% regression in memory.top_10_mobile_stress at 463379:463664

Project Member Reported by primiano@chromium.org, Apr 13 2017

Issue description

See the link to graphs below.

Comment 1 by primiano@chromium.org, Apr 13 2017

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_Kq-6woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggtTD8gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggrqTtgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggqj5oQsM


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

android-nexus5
android-nexus6
android-webview-nexus5X
android-webview-nexus6

Project Member

Comment 2 by 42576172...@developer.gserviceaccount.com, Apr 13 2017

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982421580690233584

Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 13 2017

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982421387156978736

Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Apr 13 2017


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science

Revision             Result                  N
chromium@463575      90242097 +- 500883      21      good
chromium@463664      90246583 +- 376488      21      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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile_stress

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

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


| 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 5 by 42576172...@developer.gserviceaccount.com, Apr 13 2017


=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/foreground/https_www_google_co_uk_hl_en_q_science


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_stress

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

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


| 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 6 by 42576172...@developer.gserviceaccount.com, Apr 13 2017

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982405369669365328

Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Apr 13 2017

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982405362750007040

Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Apr 13 2017


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science

Revision             Result                  N
chromium@463575      90267648 +- 127438      21      good
chromium@463664      90260821 +- 305218      21      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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile_stress

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

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


| 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, Apr 14 2017


=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/foreground/https_www_google_co_uk_hl_en_q_science


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_stress

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

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


| 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, Apr 14 2017

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982299671498882016

Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Apr 15 2017

Mergedinto: 711044
Status: Duplicate (was: Untriaged)


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

Suspected Commit
  Author : delphick
  Commit : d8ade60fbe0ea954ecd5f186c36e6d0ac045c28c
  Date   : Tue Apr 11 09:56:28 2017
  Subject: No longer clamp setTimeout(..., 0) to 1ms.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/foreground/https_www_google_co_uk_hl_en_q_science
  Change       : 82.82% | 7254354.66667 -> 1246264.0

Revision             Result                  N
chromium@463463      7254355 +- 1939340      6      good
chromium@463530      7560801 +- 1539417      6      good
chromium@463563      6722133 +- 846800       6      good
chromium@463580      7161175 +- 5242074      6      good
chromium@463588      6885215 +- 1089028      6      good
chromium@463590      8013222 +- 2899424      6      good
chromium@463591      2663180 +- 5151112      6      bad       <--
chromium@463592      2415451 +- 5102717      9      bad
chromium@463596      1246264 +- 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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile_stress

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

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


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

►

Issue 711299 link

Issue metadata

1.5%-272.3% regression in memory.top_10_mobile_stress at 463379:463664

Issue description

Comment 1 by primiano@chromium.org, Apr 13 2017

Comment 1 Deleted

Comment 2 by 42576172...@developer.gserviceaccount.com, Apr 13 2017

Comment 2 Deleted

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 13 2017

Comment 3 Deleted

Comment 4 by 42576172...@developer.gserviceaccount.com, Apr 13 2017

Comment 4 Deleted

Comment 5 by 42576172...@developer.gserviceaccount.com, Apr 13 2017

Comment 5 Deleted

Comment 6 by 42576172...@developer.gserviceaccount.com, Apr 13 2017

Comment 6 Deleted

Comment 7 by 42576172...@developer.gserviceaccount.com, Apr 13 2017

Comment 7 Deleted

Comment 8 by 42576172...@developer.gserviceaccount.com, Apr 13 2017

Comment 8 Deleted

Comment 9 by 42576172...@developer.gserviceaccount.com, Apr 14 2017

Comment 9 Deleted

Comment 10 by 42576172...@developer.gserviceaccount.com, Apr 14 2017

Comment 10 Deleted

Comment 11 by 42576172...@developer.gserviceaccount.com, Apr 15 2017

Comment 11 Deleted

Sign in to add a comment