New issue
Advanced search Search tips

Issue 865681 link

Starred by 1 user
Status: WontFix
Owner:
ilnik@chromium.org
Closed: Jul 23
Cc:
npm@chromium.org
ilnik@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 865758


Sign in to add a comment

1.3%-2.6% regression in system_health.memory_mobile at 1531927658:1531942003

Project Member Reported by npm@chromium.org, Jul 19 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 19 

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

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


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

health-plan-clankium-phone
health-plan-webview-phone
perf-go-phone-1024
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 20 


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

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size_avg/browse_news/browse_news_qq
  Change       : 0.44% | 44851395.0476 -> 45046832.7619

Revision                       Result                  N
android-chrome@478583399d      44851395 +- 386506      21      good
android-chrome@5bcd964863      45046833 +- 422861      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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.qq system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8940541609754378608


For feedback, file a bug with component Speed>Bisection

Comment 4 by npm@chromium.org, Jul 20

Blockedon: 865758
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Jul 20 


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_search/load_search_yandex


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=load.search.yandex system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8940455013392565872


For feedback, file a bug with component Speed>Bisection

Comment 9 by npm@chromium.org, Jul 20 

Trying again but this might be WontFix since theres a drop in the metric reccently so this might just be a revert of a bug
Project Member

Comment 10 by 42576172...@developer.gserviceaccount.com, Jul 22

Cc: ilnik@chromium.org
Owner: ilnik@chromium.org
Status: Assigned (was: Untriaged)

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

Hi ilnik@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 : Ilya Nikolaevskiy
  Commit : 90665ce020b9c4959dd9ba4a838e10cd04ea2627
  Date   : Wed Jul 18 07:55:28 2018
  Subject: Disable failing WebRtcVideoCapturerAdapter tests

Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/load_search/load_search_yandex
  Change       : 1.25% | 91155373.3333 -> 92299352.0

Revision                                       Result                  N
android-chrome@22c1f49355                      91155373 +- 125180      6      good
android-chrome@22c1f49355,chromium@575972      91882925 +- 226652      6      bad       <--
android-chrome@22c1f49355,chromium@575973      91893507 +- 155275      6      bad
android-chrome@22c1f49355,chromium@575974      91995224 +- 131957      6      bad
android-chrome@22c1f49355,chromium@575976      92170499 +- 172773      6      bad
android-chrome@478583399d                      92166403 +- 145401      6      bad
android-chrome@91f30dd85c                      91956483 +- 168592      6      bad
android-chrome@934b6671a2                      92299352 +- 163114      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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.search.yandex system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8940471848333662576


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Jul 22 


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

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size_avg/browse_news/browse_news_qq
  Change       : 0.06% | 44924537.9048 -> 44899766.8571

Revision                       Result                  N
android-chrome@478583399d      44924538 +- 423143      21      good
android-chrome@5bcd964863      44899767 +- 359587      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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.qq system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8940454325891390320


For feedback, file a bug with component Speed>Bisection

Comment 12 by ilnik@chromium.org, Jul 23

Status: WontFix (was: Assigned)
It's just a noise: The commit in question only deletes few tests related to webrtc. In no way could it possibly cause any change in memory consumption.
►

Sign in to add a comment