Issue metadata
Sign in to add a comment
|
5.5%-6.1% regression in system_health.memory_mobile at 512063:512117 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 31 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8964184423609337184
,
Nov 1 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Nicholas Verne Commit : 5420564de0e2b7da728e7a9402e04b6cdfb9fc0a Date : Fri Oct 27 07:37:54 2017 Subject: Mojoify control messages for child processes. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_chrome/browse_chrome_newtab Change : 4.28% | 34140673.3333 -> 35607278.6667 Revision Result N chromium@512062 34140673 +- 1095983 6 good chromium@512090 33635500 +- 754309 6 good chromium@512104 33966959 +- 608089 6 good chromium@512111 33701593 +- 731947 9 good chromium@512114 34147927 +- 3239014 9 good chromium@512115 35782496 +- 1741770 9 bad <-- chromium@512116 35589886 +- 1488272 9 bad chromium@512117 35607279 +- 923439 9 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 --story-filter=browse.chrome.newtab 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/8964184423609337184 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 31 2017