Issue metadata
Sign in to add a comment
|
4.7%-8.9% regression in performance_browser_tests at 526685:526987 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 8 2018
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8957930543484946304
,
Jan 9 2018
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : George Burgess IV Commit : 274d75742451914f74bbad40c405da7f902dd232 Date : Wed Jan 03 23:22:46 2018 Subject: Turn on AFDO for Chromium on Android Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : thread_times.tough_scrolling_cases Metric : thread_raster_cpu_time_per_frame/text_50000_pixels_per_second Change : 9.79% | 5.88167362869 -> 6.45773930888 Revision Result N chromium@526694 5.88167 +- 0.18662 6 good chromium@526841 6.00088 +- 0.173213 6 good chromium@526851 5.97948 +- 0.339942 9 good chromium@526856 6.07634 +- 0.602809 9 good chromium@526857 5.94137 +- 0.191154 6 good chromium@526858 6.48144 +- 0.272611 6 bad <-- chromium@526860 6.50414 +- 0.519375 9 bad chromium@526878 6.53769 +- 0.531377 6 bad chromium@526914 6.46415 +- 0.376205 6 bad chromium@526987 6.45774 +- 0.461827 6 bad 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 --story-filter=text.50000.pixels.per.second thread_times.tough_scrolling_cases More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8957930543484946304 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jan 8 2018