Issue metadata
Sign in to add a comment
|
1%-2.6% regression in memory.top_10_mobile at 474308:474371 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 26 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978491213402589728
,
May 27 2017
=== Auto-CCing suspected CL author fdoray@chromium.org === Hi fdoray@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : fdoray Commit : b87bcfb8c3b17bbcad020186a94e935e2fd0d162 Date : Wed May 24 17:49:40 2017 Subject: [reland] Use TaskScheduler instead of WorkerPool in v8_platform.cc. Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/foreground/https_mobile_twitter_com_justinbieber_skip_interstitial_true Change : 3.36% | 34825724.6667 -> 35995280.6667 Revision Result N chromium@474307 34825725 +- 828837 6 good chromium@474329 34557769 +- 1522731 6 good chromium@474340 34375066 +- 862268 6 good chromium@474345 34719231 +- 1112988 9 good chromium@474346 35359453 +- 1421513 14 bad <-- chromium@474347 35412229 +- 930499 9 bad chromium@474348 35681125 +- 961284 6 bad chromium@474350 35995281 +- 650439 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-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/8978491213402589728 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6132109212647424 | 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 28 2017
Issue 726899 has been merged into this issue.
,
May 30 2017
,
May 30 2017
,
Jun 6 2017
Issue 727509 has been merged into this issue.
,
Jun 13 2017
Issue 726903 has been merged into this issue.
,
Jun 13 2017
Issue 726903 has been merged into this issue.
,
Jun 13 2017
Issue 726922 has been merged into this issue.
,
Jun 16 2017
,
Jun 20 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976260272144400816
,
Jun 20 2017
Above is a bisect of the improvement in https://chromeperf.appspot.com/report?sid=bd70588901689258e6a3981383ae230ea41045769748af7e78652b211238a63b&rev=474350
,
Jun 20 2017
=== BISECT JOB RESULTS === Perf regression found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : v8.runtimestats.browsing_mobile Metric : v8-gc-total_max/browse_media/browse_media_imgur Change : 54.15% | 68.537 -> 35.9456666667 Suspected Commit Range 2 commits in range https://chromium.googlesource.com/chromium/src/+log/168444cf44dfed8b347a5fbaf4420a6733e11e2d..6eb5c1eb647e1709b4b03ae5148f8c03daea03fb Revision Result N chromium@474752 68.537 +- 88.3777 14 good chromium@474760 65.3543 +- 73.7399 14 good chromium@474761 --- --- build failure chromium@474762 40.3543 +- 33.8716 14 bad chromium@474763 40.2683 +- 27.486 9 bad chromium@474766 39.7714 +- 24.0455 14 bad chromium@474779 41.032 +- 14.8082 9 bad chromium@474805 31.1821 +- 20.1591 9 bad chromium@474857 35.9457 +- 14.7867 9 bad 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.media.imgur v8.runtimestats.browsing_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976260272144400816 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5801742517665792 | 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!
,
Jun 20 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : fdoray Commit : 6eb5c1eb647e1709b4b03ae5148f8c03daea03fb Date : Thu May 25 19:51:13 2017 Subject: Update TaskTraits in v8_platform.cc. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : v8.runtimestats.browsing_mobile Metric : v8-gc-total_max/browse_media/browse_media_imgur Change : 47.23% | 60.4248571429 -> 31.8863571429 Revision Result N chromium@474752 60.4249 +- 93.8387 14 good chromium@474759 78.523 +- 31.7173 6 good chromium@474761 60.3803 +- 35.1906 6 good chromium@474762 34.6617 +- 12.0309 6 bad <-- chromium@474766 31.7456 +- 27.8149 14 bad chromium@474780 36.5483 +- 40.601 21 bad chromium@474805 35.81 +- 40.5049 21 bad chromium@474857 31.8864 +- 27.0109 14 bad 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.media.imgur v8.runtimestats.browsing_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976260279720539376 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5241812463124480 | 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 briander...@chromium.org
, May 26 2017