Issue metadata
Sign in to add a comment
|
1.5%-25% regression in memory.top_10_mobile at 463183:463209 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 19 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981887979261634800
,
Apr 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981705051938329808
,
Apr 24 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981432744689430816
,
Apr 25 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/background/after_https_m_facebook_com_rihanna 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 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981432744689430816 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5814285474725888 | 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 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980663330248583408
,
May 3 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : peria Commit : 91ee8664ce7bc2a8fc792c6144cc8dd4408402b9 Date : Mon Apr 10 08:47:02 2017 Subject: Remove V8HiddenValue class. Bisect Details Configuration: android_one_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_www_baidu_com_s_word_google Change : 1.20% | 4049292.66667 -> 4097738.0 Revision Result N chromium@463185 4049293 +- 8145.28 6 good chromium@463191 4049702 +- 21458.8 6 good chromium@463194 4049294 +- 8133.72 6 good chromium@463196 4050700 +- 20994.5 6 good chromium@463197 4097545 +- 14025.4 6 bad <-- chromium@463209 4097738 +- 13198.8 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/8980663330248583408 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5814285474725888 | 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 alexclarke@chromium.org
, Apr 19 2017