Issue metadata
Sign in to add a comment
|
26.7%-29.8% regression in system_health.memory_mobile at 512063:512122 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 31 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8964184415641427008
,
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_chrome:java_heap:effective_size_avg/browse_chrome/browse_chrome_newtab Change : 29.74% | 58385066.6667 -> 75748010.6667 Revision Result N chromium@512062 58385067 +- 70331.2 6 good chromium@512090 58341376 +- 201725 6 good chromium@512104 58410325 +- 210987 6 good chromium@512111 58363904 +- 121369 6 good chromium@512114 58429440 +- 157683 6 good chromium@512115 75757568 +- 397745 6 bad <-- chromium@512116 75684523 +- 170136 6 bad chromium@512117 75748011 +- 132525 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-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/8964184415641427008 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