Issue metadata
Sign in to add a comment
|
4.1%-87975.6% regression in system_health.memory_mobile at 1530653166:1531279570 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 16
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8940834099699594416
,
Jul 16
=== 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_chrome:gpu:effective_size_avg/browse_social/browse_social_facebook_infinite_scroll 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=browse.social.facebook.infinite.scroll 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/8940834099699594416 For feedback, file a bug with component Speed>Bisection
,
Jul 23
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8940213703195427680
,
Jul 23
This is a pretty widespread and large regression. Let's try to figure out if it's intended.
,
Jul 23
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Khushal Commit : 81a71217973e595b574783c2496629311051450f Date : Mon Jul 09 22:48:23 2018 Subject: gpu: Add memory tracing for ServiceTransferCache. Bisect Details Configuration: clankium-phone-perf-bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/load_media/load_media_imgur Change : 5049.70% | 2108620.0 -> 108587576.0 Revision Result N android-chrome@96555ff9c3 2108620 +- 0.0 6 good android-chrome@96555ff9c3,chromium@573466 2108620 +- 0.0 6 good android-chrome@96555ff9c3,chromium@573486 2108620 +- 0.0 6 good android-chrome@96555ff9c3,chromium@573491 2108620 +- 0.0 6 good android-chrome@96555ff9c3,chromium@573494 2108620 +- 0.0 6 good android-chrome@96555ff9c3,chromium@573495 2108620 +- 0.0 6 good android-chrome@96555ff9c3,chromium@573496 108587576 +- 0.0 6 bad <-- android-chrome@96555ff9c3,chromium@573506 108587576 +- 0.0 6 bad android-chrome@96555ff9c3,chromium@573545 108587576 +- 0.0 6 bad android-chrome@0c23a72c68 108587576 +- 0.0 6 bad android-chrome@7b94b395a3 108587576 +- 0.0 6 bad android-chrome@cd63705090 108587576 +- 0.0 6 bad android-chrome@cb4b582a48 108587576 +- 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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.media.imgur 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/8940213703195427680 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 16