Issue metadata
Sign in to add a comment
|
95.7% improvement in system_health.memory_mobile at 470433:470513 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979554059505529376
,
May 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979554042362352832
,
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_nexus6_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/browse_shopping/browse_shopping_avito Change : 79.49% | 15324328.0 -> 3142374.66667 Revision Result N chromium@470432 15324328 +- 34053402 14 good chromium@470473 17700054 +- 18393169 6 good chromium@470483 17704187 +- 18335020 6 good chromium@470488 17717064 +- 18340611 6 good chromium@470489 18310932 +- 19265358 6 good chromium@470490 4260761 +- 18389141 6 bad <-- chromium@470491 903121 +- 7040.06 6 bad chromium@470493 901836 +- 0.0 6 bad chromium@470513 3142375 +- 19011601 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 --story-filter=browse.shopping.avito system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979554042362352832 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5045319512883200 | 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_nexus6_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/browse_shopping/browse_shopping_avito Change : 51.40% | 21065428.4444 -> 10238138.6667 Revision Result N chromium@470432 21065428 +- 15958.4 9 good chromium@470473 21081350 +- 164321 9 good chromium@470483 21688083 +- 3223055 6 good chromium@470488 21073092 +- 39347.6 6 good chromium@470489 21067961 +- 11678.5 6 good chromium@470490 4251935 +- 18353803 6 bad <-- chromium@470491 894567 +- 52442.1 6 bad chromium@470493 4252627 +- 18353040 6 bad chromium@470513 10238139 +- 31497992 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 --story-filter=browse.shopping.avito system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979554059505529376 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5872743989379072 | 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