Issue metadata
Sign in to add a comment
|
10.9% regression in system_health.memory_mobile at 478668:478744 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976903966982639296
,
Jun 15 2017
=== BISECT JOB RESULTS === Perf regression found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. 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/background_news/background_news_nytimes Change : 7.35% | 28775775.1429 -> 30999304.8571 Suspected Commit Range 2 commits in range https://chromium.googlesource.com/chromium/src/+log/964fc7fe50b27ffb527e3e237e46650c18599578..db76a97fd74c4ee0e5f4c379a1289ee0f44ed7ea Revision Result N chromium@478667 28775775 +- 4714548 14 good chromium@478706 28994825 +- 7182022 21 good chromium@478716 28493250 +- 4757626 14 good chromium@478721 28938366 +- 7591933 21 good chromium@478723 27887721 +- 873471 6 good chromium@478724 28083945 +- 2665827 6 good chromium@478725 --- --- build failure chromium@478726 30825037 +- 5735395 14 bad chromium@478744 30999305 +- 2050195 14 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=background.news.nytimes system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976903966982639296 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5538453523005440 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Jun 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976721616832812192
,
Jun 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976721510029883072
,
Jun 15 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Marijn Kruisselbrink Commit : dda8780efac5966b275b8b7beeabe951b9d9c133 Date : Mon Jun 12 19:42:06 2017 Subject: Implement retry behavior for several leveldb env methods in mojo env. Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/browse_chrome/browse_chrome_omnibox Change : 1.36% | 17480021.3333 -> 17718613.3333 Revision Result N chromium@478590 17480021 +- 137618 6 good chromium@478667 17468075 +- 147048 6 good chromium@478706 17425067 +- 120490 6 good chromium@478716 17491968 +- 199992 6 good chromium@478719 17506645 +- 128051 6 good chromium@478720 17794048 +- 95314.5 6 bad <-- chromium@478721 17734315 +- 128916 6 bad chromium@478725 17749333 +- 165411 6 bad chromium@478744 17718613 +- 146734 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.omnibox system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976721510029883072 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5053767604502528 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Jun 16 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Marijn Kruisselbrink Commit : dda8780efac5966b275b8b7beeabe951b9d9c133 Date : Mon Jun 12 19:42:06 2017 Subject: Implement retry behavior for several leveldb env methods in mojo env. 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_media/load_media_imgur Change : 12.42% | 11567021.7778 -> 12917628.4444 Revision Result N chromium@478667 11567022 +- 970409 9 good chromium@478706 11533592 +- 712510 9 good chromium@478716 11477844 +- 455464 6 good chromium@478719 11467235 +- 417972 6 good chromium@478720 12877689 +- 2153865 9 bad <-- chromium@478721 12877694 +- 1363080 6 bad chromium@478725 12352950 +- 2874941 14 bad chromium@478744 12917628 +- 1831506 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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.media.imgur system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976721616832812192 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4575438438924288 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by alexclarke@chromium.org
, Jun 13 2017