Issue metadata
Sign in to add a comment
|
77.1% regression in thread_times.simple_mobile_sites at 481163:481215 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 23 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976005297687002592
,
Jun 23 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976005291009100704
,
Jun 23 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Dave Tapuska Commit : 4cef659a8009c5cb4f5708336ae37654d23653b3 Date : Wed Jun 21 15:16:45 2017 Subject: Enable scrollTopLeftInterop by default. Bisect Details Configuration: android_one_perf_bisect Benchmark : thread_times.simple_mobile_sites Metric : thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame Change : 96.52% | 22.5899976945 -> 44.3943065328 Revision Result N chromium@481162 22.59 +- 1.40683 6 good chromium@481189 22.4193 +- 0.959131 6 good chromium@481202 22.3261 +- 1.40761 6 good chromium@481206 22.6486 +- 0.605825 6 good chromium@481207 23.0365 +- 0.582818 6 good chromium@481208 40.7332 +- 4.1489 6 bad <-- chromium@481209 42.7201 +- 6.52172 6 bad chromium@481215 44.3943 +- 6.90933 6 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 thread_times.simple_mobile_sites Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976005291009100704 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5347258070990848 | 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 23 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Dave Tapuska Commit : 4cef659a8009c5cb4f5708336ae37654d23653b3 Date : Wed Jun 21 15:16:45 2017 Subject: Enable scrollTopLeftInterop by default. Bisect Details Configuration: android_one_perf_bisect Benchmark : thread_times.simple_mobile_sites Metric : thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame Change : 67.27% | 16.1423079213 -> 27.0018079208 Revision Result N chromium@481162 16.1423 +- 0.877358 6 good chromium@481189 15.9906 +- 0.616736 6 good chromium@481202 16.0286 +- 0.964338 6 good chromium@481206 16.3518 +- 0.874897 6 good chromium@481207 16.237 +- 0.981032 6 good chromium@481208 26.8787 +- 3.46574 6 bad <-- chromium@481209 28.4475 +- 3.85681 6 bad chromium@481215 27.0018 +- 2.46824 6 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 thread_times.simple_mobile_sites Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976005297687002592 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6361935504736256 | 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 kraynov@chromium.org
, Jun 23 2017