Issue metadata
Sign in to add a comment
|
4.8%-23.8% regression in thread_times.tough_scrolling_cases at 526647:526987 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 5 2018
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8958197226040312784
,
Jan 6 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_nexus7_perf_bisect Benchmark : thread_times.tough_scrolling_cases Metric : thread_raster_cpu_time_per_frame/canvas_15000_pixels_per_second Change : 15.20% | 2.35370238856 -> 2.71155141512 Revision Result N chromium@526662 2.3537 +- 0.108535 6 good chromium@526818 2.33081 +- 0.080905 6 good chromium@526857 2.33198 +- 0.0787534 6 good chromium@526858 2.67388 +- 0.0485809 6 bad <-- chromium@526859 2.6578 +- 0.0471432 6 bad chromium@526860 2.71616 +- 0.172029 6 bad chromium@526862 2.7004 +- 0.0741899 6 bad chromium@526867 2.66456 +- 0.0735583 6 bad chromium@526877 2.6836 +- 0.113013 6 bad chromium@526896 2.67689 +- 0.0803952 6 bad chromium@526974 2.71155 +- 0.192203 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=canvas.15000.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/8958197226040312784 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jan 5 2018