Issue metadata
Sign in to add a comment
|
9.8% regression in system_health.memory_mobile at 515477:515515 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8963023461126828560
,
Nov 14 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/load_games/load_games_bubbles Revision Result N chromium@515476 6918452 +- 2049356 21 good chromium@515515 6983653 +- 2367431 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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.games.bubbles 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/8963023461126828560 For feedback, file a bug with component Speed>Bisection
,
Nov 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8962852308874685584
,
Nov 15 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Michael Starzinger Commit : 23883b85f21a2c61515cb57064b19901ae666884 Date : Thu Nov 09 09:31:15 2017 Subject: [deoptimizer] Turn deopt entries into immovable Code objects. Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/load_games/load_games_bubbles Change : 12.38% | 6459998.0 -> 7275150.66667 Revision Result N chromium@515129 6459998 +- 164048 14 good chromium@515226 6562838 +- 2292289 21 good chromium@515274 6577172 +- 2460699 21 good chromium@515286 6526527 +- 2341357 21 good chromium@515289 6555222 +- 1869306 14 good chromium@515289,v8@23883b85f2 7042254 +- 2548829 21 bad <-- chromium@515289,v8@b9c9932202 6909427 +- 2043232 21 bad chromium@515289,v8@8ba40216db 7033749 +- 1890108 14 bad chromium@515289,v8@c899637deb 7105154 +- 2696794 21 bad chromium@515290 6937243 +- 2022321 19 bad chromium@515291 7009517 +- 1908470 14 bad chromium@515292 7207760 +- 1744035 9 bad chromium@515298 6945298 +- 1705149 14 bad chromium@515322 7049652 +- 1841231 14 bad chromium@515515 7275151 +- 1361066 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=load.games.bubbles 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/8962852308874685584 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 13 2017