Issue metadata
Sign in to add a comment
|
1%-2700.4% regression in memory.top_10_mobile at 477921:478098 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977002001887855664
,
Jun 12 2017
=== BISECT JOB RESULTS === NO Perf regression found 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 Revision Result N chromium@477943 3670560 +- 11469252 21 good chromium@477960 3164919 +- 12040206 21 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/8977002001887855664 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6102996506640384 | 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 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976981752224492784
,
Jun 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976981722426144448
,
Jun 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976981691451382720
,
Jun 13 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:java_heap:effective_size_avg/load_search/load_search_baidu Revision Result N chromium@477900 61897569 +- 7292945 21 good chromium@478100 62474193 +- 8739512 21 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=load.search.baidu system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976981752224492784 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5602998157312000 | 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 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976891095908442416
,
Jun 13 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:java_heap:effective_size_avg/load_search/load_search_baidu Revision Result N chromium@477900 61897569 +- 7292945 21 good chromium@478100 62474193 +- 8739512 21 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=load.search.baidu system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976891095908442416 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5602998157312000 | 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 13 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:webview:all_processes:reported_by_chrome:skia:effective_size_avg/browse_shopping/browse_shopping_avito Revision Result N chromium@477600 885049 +- 79980.7 21 good chromium@477999 12648942 +- 46808762 21 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/8976981722426144448 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5902312280686592 | 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 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976875996075035840
,
Jun 13 2017
=== BISECT JOB RESULTS === NO Perf regression found 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 Revision Result N chromium@477943 2659278 +- 12151178 21 good chromium@477960 2912098 +- 12151178 21 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/8976981691451382720 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6102996506640384 | 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 14 2017
The bots aren't finding anything, I think we can close this.
,
Jun 15 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:webview:all_processes:reported_by_chrome:skia:effective_size_avg/browse_shopping/browse_shopping_avito Change : 1276.85% | 883130.666667 -> 12159408.8889 Revision Result N chromium@477600 883131 +- 26795.3 9 good chromium@477999 12159409 +- 30225350 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/8976875996075035840 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5902312280686592 | 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 12 2017