Issue metadata
Sign in to add a comment
|
8.5%-205.4% regression in thread_times.key_mobile_sites_smooth at 513500:513853 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 6 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8963658744059159216
,
Nov 6 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_nexus5_perf_bisect Benchmark : thread_times.key_mobile_sites_smooth Metric : thread_other_cpu_time_per_frame/http___cuteoverload.com Change : 212.12% | 0.0844496777173 -> 0.263584752232 Suspected Commit Range 3 commits in range https://chromium.googlesource.com/v8/v8.git/+log/a274fc653686179346e8a3002e63c5db5b71a033..586067e45dd542a117b67ad66d3b14475d8d571f Revision Result N chromium@513499 0.0844497 +- 0.167851 6 good chromium@513676 0.070671 +- 0.033526 6 good chromium@513699 0.0829103 +- 0.043477 6 good chromium@513710 0.0777868 +- 0.0569088 6 good chromium@513716 0.0618471 +- 0.0426479 6 good chromium@513719 0.073601 +- 0.0598291 6 good chromium@513719,v8@a274fc6536 0.0684709 +- 0.0544536 6 good chromium@513719,v8@fd35526f36 --- --- build failure chromium@513719,v8@694a18781c --- --- build failure chromium@513719,v8@586067e45d 0.255772 +- 0.0548692 6 bad chromium@513720 0.250684 +- 0.0173629 6 bad chromium@513721 0.267578 +- 0.046015 6 bad chromium@513765 0.257587 +- 0.0447848 6 bad chromium@513853 0.263585 +- 0.063502 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 --story-filter=http...cuteoverload.com thread_times.key_mobile_sites_smooth More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8963658744059159216 For feedback, file a bug with component Speed>Bisection
,
Nov 7 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8963550691834229344
,
Nov 7 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Matthew Jones Commit : 95f29fcd6f90903cbfbd71bbe6205d75cd55e915 Date : Fri Nov 03 14:52:51 2017 Subject: Remove throttled-progress updates flag Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : thread_times.key_mobile_sites_smooth Metric : thread_browser_cpu_time_per_frame/http___cuteoverload.com Change : 29.25% | 3.92224725321 -> 5.06945019656 Revision Result N chromium@513499 3.92225 +- 0.0345623 6 good chromium@513676 3.9268 +- 0.0635926 6 good chromium@513765 3.90285 +- 0.062737 6 good chromium@513768 3.8904 +- 0.043884 6 good chromium@513769 3.90199 +- 0.0538348 6 good chromium@513770 5.09406 +- 0.14854 6 bad <-- chromium@513771 5.05838 +- 0.227113 6 bad chromium@513776 5.06253 +- 0.117232 6 bad chromium@513787 5.06486 +- 0.0993676 6 bad chromium@513809 5.06027 +- 0.150807 6 bad chromium@513853 5.06945 +- 0.113528 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 --story-filter=http...cuteoverload.com thread_times.key_mobile_sites_smooth More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8963550691834229344 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 6 2017