Issue metadata
Sign in to add a comment
|
9.6%-41.7% regression in system_health.memory_mobile at 509898:509967 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 20 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8965206174118741328
,
Oct 21 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Eric Karl Commit : 840b7a60cc3c5f802ca271bd167e888e7494e8aa Date : Wed Oct 18 22:39:08 2017 Subject: [Re-Land] Use GPU Discardable in Image Decode Cache Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:webview:all_processes:reported_by_chrome:cc:effective_size_avg/browse_social/browse_social_facebook_infinite_scroll Change : 39.44% | 285227588.667 -> 397726891.333 Revision Result N chromium@509897 285227589 +- 8130968 6 good chromium@509900 287041541 +- 13533869 6 good chromium@509901 285787976 +- 13635755 6 good chromium@509902 391320539 +- 33579863 6 bad <-- chromium@509906 396807449 +- 10242024 6 bad chromium@509915 396348552 +- 22306595 6 bad chromium@509932 400672922 +- 16728653 6 bad chromium@509967 397726891 +- 13370462 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=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/8965206174118741328 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 20 2017