Issue metadata
Sign in to add a comment
|
2.3%-4.4% regression in system_health.memory_mobile at 523361:523527 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8960213693226990480
,
Dec 15 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Yutaka Hirano Commit : 47b8f2451e900fe2c5fc4d94046925f40fea2fc7 Date : Tue Dec 12 10:52:56 2017 Subject: Update RendererSideResourceScheduler testing config Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/load_social/load_social_twitter Change : 3.78% | 24529462.6667 -> 25456141.3333 Revision Result N chromium@523387 24529463 +- 377354 6 good chromium@523392 24256615 +- 472520 6 good chromium@523394 24572087 +- 405456 6 good chromium@523395 24398555 +- 469025 6 good chromium@523396 25267179 +- 496339 6 bad <-- chromium@523405 25326921 +- 578824 6 bad chromium@523422 25165611 +- 182792 6 bad chromium@523457 25329057 +- 552366 6 bad chromium@523527 25456141 +- 801472 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.social.twitter 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/8960213693226990480 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Dec 14 2017