Issue metadata
Sign in to add a comment
|
11.4% regression in memory.top_10_mobile at 468954:469009 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980431539463082656
,
May 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980431526100331296
,
May 5 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : kbr Commit : 1d44ab0e3d0a7cd05ce1da956bb87a85a8b88174 Date : Wed May 03 16:54:08 2017 Subject: Fix bug in virtualized GL context state management upon creation. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_www_baidu_com_s_word_google Change : 11.17% | 69989034.6667 -> 77806933.3333 Revision Result N chromium@468953 69989035 +- 661613 6 good chromium@468981 69888000 +- 119383 6 good chromium@468995 69866837 +- 61485.5 6 good chromium@469002 69855915 +- 4729.65 6 good chromium@469006 69855232 +- 92817.6 6 good chromium@469007 77797376 +- 74576.5 6 bad <-- chromium@469008 76511915 +- 7222744 6 bad chromium@469009 77806933 +- 57757.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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980431539463082656 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5882012495249408 | 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 6 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : kbr Commit : 1d44ab0e3d0a7cd05ce1da956bb87a85a8b88174 Date : Wed May 03 16:54:08 2017 Subject: Fix bug in virtualized GL context state management upon creation. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_www_baidu_com_s_word_google Change : 9.50% | 69855914.6667 -> 76932437.3333 Revision Result N chromium@468953 69855915 +- 4729.65 6 good chromium@468981 69862286 +- 64446.0 9 good chromium@468995 69855004 +- 6105.96 9 good chromium@469002 70189966 +- 1076302 9 good chromium@469006 69844309 +- 57757.0 6 good chromium@469007 77937323 +- 587563 6 bad <-- chromium@469008 77830144 +- 60684.4 6 bad chromium@469009 76932437 +- 7504339 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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980431526100331296 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5902159381528576 | 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 kraynov@chromium.org
, May 5 2017