Issue metadata
Sign in to add a comment
|
97.6% improvement in system_health.memory_mobile at 470446:470497 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979554228188117536
,
May 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979554218139691760
,
May 15 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : yhirano Commit : 91088a195969f5af61f404c9f02edc622cbe373a Date : Wed May 10 05:49:31 2017 Subject: Add Field Trial Testing Configuration for MojoLoading Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:webview:all_processes:reported_by_chrome:gpu:effective_size_avg/browse_shopping/browse_shopping_avito Change : 84.60% | 4681842.28571 -> 720986.666667 Revision Result N chromium@470445 4681842 +- 6951416 14 good chromium@470471 5440304 +- 0.0 6 good chromium@470484 5061073 +- 5116104 14 good chromium@470488 3923381 +- 8974240 14 good chromium@470489 5440304 +- 0.0 6 good chromium@470490 889534 +- 6951416 14 bad <-- chromium@470491 889534 +- 6951416 14 bad chromium@470497 720987 +- 5005592 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=browse.shopping.avito system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979554228188117536 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6291028337754112 | 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!
,
May 15 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : yhirano Commit : 91088a195969f5af61f404c9f02edc622cbe373a Date : Wed May 10 05:49:31 2017 Subject: Add Field Trial Testing Configuration for MojoLoading Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:webview:all_processes:reported_by_chrome:gpu:effective_size_avg/browse_shopping/browse_shopping_avito Change : 97.12% | 4555432.0 -> 131072.0 Revision Result N chromium@470445 4555432 +- 4846644 6 good chromium@470471 4555432 +- 4846644 6 good chromium@470484 4555432 +- 4846644 6 good chromium@470488 5440304 +- 0.0 6 good chromium@470489 5440304 +- 0.0 6 good chromium@470490 131072 +- 0.0 6 bad <-- chromium@470491 131072 +- 0.0 6 bad chromium@470497 131072 +- 0.0 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=browse.shopping.avito system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979554218139691760 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6013043558842368 | 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 yhirano@chromium.org
, May 15 2017