Issue metadata
Sign in to add a comment
|
1.4%-128.1% regression in memory.top_10_mobile at 470449:470497 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979945259970550352
,
May 12 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : memory.top_10_mobile_stress Metric : memory:webview:all_processes:reported_by_chrome:gpu:effective_size_avg/foreground/https_mobile_twitter_com_justinbieber_skip_interstitial_true Revision Result N chromium@470448 17027346 +- 1162359 21 good chromium@470490 26238039 +- 59563881 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 memory.top_10_mobile_stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979945259970550352 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5241528047370240 | 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 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979827949234908432
,
May 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979796482510968288
,
May 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979796476773352800
,
May 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979796468687487376
,
May 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979796417883911808
,
May 12 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_nexus6_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/browse_news/browse_news_toi Change : 9.69% | 228162218.667 -> 250272426.667 Revision Result N chromium@470432 228162219 +- 6128059 6 good chromium@470473 228178603 +- 4875313 6 good chromium@470483 228726101 +- 1555646 6 good chromium@470488 228738389 +- 1684743 6 good chromium@470489 228044800 +- 5839531 6 good chromium@470490 248979456 +- 7491637 6 bad <-- chromium@470491 248900267 +- 9759761 6 bad chromium@470493 247124651 +- 11704270 6 bad chromium@470513 250272427 +- 10231584 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.news.toi system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979796417883911808 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5804200774074368 | 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 12 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : dominickn Commit : faace60759ac73ae60b5d4ef84fb85c65c937b4a Date : Wed May 10 08:45:47 2017 Subject: Add blocking permission prompts to the field trial testing config. Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/background/after_http_m_intl_taobao_com_group_purchase_html Change : 10.55% | 24925525.3333 -> 27555157.3333 Revision Result N chromium@470463 24925525 +- 14956.5 6 good chromium@470492 22170965 +- 19612405 6 good chromium@470507 25788416 +- 960318 6 good chromium@470514 25794560 +- 967068 6 good chromium@470518 22519808 +- 20015817 6 good chromium@470520 25441621 +- 1284377 6 good chromium@470521 27555157 +- 1939885 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/8979796476773352800 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5897252314284032 | 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 13 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : memory.top_10_mobile_stress Metric : memory:webview:all_processes:reported_by_chrome:gpu:effective_size_avg/foreground/https_mobile_twitter_com_justinbieber_skip_interstitial_true Revision Result N chromium@470448 16669172 +- 8184157 21 good chromium@470490 24928171 +- 57072301 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 memory.top_10_mobile_stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979827949234908432 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5241528047370240 | 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 13 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : dominickn Commit : faace60759ac73ae60b5d4ef84fb85c65c937b4a Date : Wed May 10 08:45:47 2017 Subject: Add blocking permission prompts to the field trial testing config. Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/background/after_http_www_baidu_com_s_word_google Change : 1.58% | 55821585.1429 -> 56524634.8571 Revision Result N chromium@470463 55821585 +- 3253697 14 good chromium@470493 55653941 +- 4217955 14 good chromium@470508 56121764 +- 1424216 14 good chromium@470514 55303829 +- 6331390 21 good chromium@470518 55290956 +- 3935834 9 good chromium@470520 55131991 +- 5160987 14 good chromium@470521 56524635 +- 949828 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-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/8979796468687487376 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5257580286312448 | 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 13 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:cc:effective_size_avg/load_social/load_social_pinterest Change : 38.57% | 33292416.0 -> 46134640.0 Revision Result N chromium@470445 33292416 +- 0.0 6 good chromium@470471 33292416 +- 0.0 6 good chromium@470484 33292416 +- 0.0 9 good chromium@470488 33292416 +- 0.0 6 good chromium@470489 33292416 +- 0.0 6 good chromium@470490 43994269 +- 11723293 6 bad <-- chromium@470491 42465433 +- 21707321 14 bad chromium@470497 46134640 +- 0.0 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.social.pinterest system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979796482510968288 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5857084169519104 | 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 sullivan@chromium.org
, May 10 2017