Issue metadata
Sign in to add a comment
|
44.3% improvement in memory.top_10_mobile_stress at 470449:470509 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979537478375645072
,
May 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979537469515361600
,
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_nexus5_perf_bisect Benchmark : memory.top_10_mobile_stress Metric : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/foreground/http_m_youtube_com_results_q_science Change : 41.66% | 36337332.0 -> 21200145.3333 Revision Result N chromium@470448 36337332 +- 2311015 6 good chromium@470479 35087081 +- 3003523 6 good chromium@470487 36338796 +- 3157991 6 good chromium@470489 36338796 +- 3157991 6 good chromium@470490 21090167 +- 2396946 6 bad <-- chromium@470491 20852084 +- 5667053 6 bad chromium@470494 21731815 +- 9511999 6 bad chromium@470509 21200145 +- 5319800 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_stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979537469515361600 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5871298632220672 | 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_nexus5_perf_bisect Benchmark : memory.top_10_mobile_stress Metric : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/foreground/http_m_youtube_com_results_q_science Change : 31.87% | 35116940.4444 -> 23926470.6667 Revision Result N chromium@470448 35116940 +- 15776714 9 good chromium@470479 36160385 +- 2097971 5 good chromium@470487 35805049 +- 2865100 6 good chromium@470489 36316951 +- 2796953 6 good chromium@470490 20257241 +- 3984512 6 bad <-- chromium@470491 24689510 +- 10187255 6 bad chromium@470494 21795588 +- 3942433 6 bad chromium@470509 23926471 +- 12090280 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_stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979537478375645072 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6711310886109184 | 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