Issue metadata
Sign in to add a comment
|
1.2%-34% regression in memory.top_10_mobile_stress at 444483:444621 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 20 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8989931228663930352
,
Jan 20 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : memory.top_10_mobile_stress Metric : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/foreground/https_m_facebook_com_rihanna Revision Result N chromium@444532 18168052 +- 2484661 21 good chromium@444590 18305707 +- 1865221 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=https.m.facebook.com.rihanna memory.top_10_mobile_stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8989931228663930352 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6402777191809024 | 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 Tests>AutoBisect. Thank you!
,
Jan 20 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8989922525467917104
,
Jan 20 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8989922470486326000
,
Jan 20 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : memory.top_10_mobile_stress Metric : memory:chrome:all_processes:reported_by_chrome:java_heap:effective_size_avg/foreground/http_www_amazon_com_gp_aw_s_k_nexus Revision Result N chromium@444511 54841344 +- 226654 21 good chromium@444568 54846025 +- 184118 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=http.www.amazon.com.gp.aw.s.k.nexus memory.top_10_mobile_stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8989922525467917104 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4945666586968064 | 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 Tests>AutoBisect. Thank you!
,
Jan 20 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : zqzhang Commit : a66fe8713400ed760cd5d78931e536f33c5828d5 Date : Wed Jan 18 22:36:39 2017 Subject: [Media>UI] Make ideal media image size independent of screen density Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : memory.top_10_mobile_stress Metric : memory:chrome:all_processes:reported_by_chrome:java_heap:effective_size_avg/foreground/http_yandex_ru_touchsearch_text_science Change : 3.52% | 31393109.3333 -> 32499712.0 Revision Result N chromium@444511 31393109 +- 109550 6 good chromium@444516 31420416 +- 107905 6 good chromium@444517 31423147 +- 144545 6 good chromium@444518 32496299 +- 224845 6 bad <-- chromium@444520 32473088 +- 129915 6 bad chromium@444528 32445099 +- 88119.5 6 bad chromium@444545 32493568 +- 79424.4 6 bad chromium@444579 32499712 +- 96016.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 --story-filter=http.yandex.ru.touchsearch.text.science memory.top_10_mobile_stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8989922470486326000 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5337374684348416 | 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 Tests>AutoBisect. Thank you!
,
Apr 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982675070799338352
,
Apr 10 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : memory.top_10_mobile_stress Metric : memory:chrome:all_processes:reported_by_chrome:java_heap:effective_size_avg/foreground/http_www_amazon_com_gp_aw_s_k_nexus Revision Result N chromium@444511 54841344 +- 226654 21 good chromium@444568 54846025 +- 184118 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=http.www.amazon.com.gp.aw.s.k.nexus memory.top_10_mobile_stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982675070799338352 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4945666586968064 | 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 mustaq@chromium.org
, Jan 20 2017