Issue metadata
Sign in to add a comment
|
2%-22.2% regression in blink_perf.image_decoder at 526726:526907 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 8 2018
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8957937154386407056
,
Jan 8 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 : blink_perf.image_decoder Metric : decode-lossless-webp/decode-lossless-webp Change : 18.47% | 445.064875 -> 527.281666667 Revision Result N chromium@526795 445.065 +- 5.34545 6 good chromium@526833 447.565 +- 5.98024 6 good chromium@526852 443.495 +- 2.87317 6 good chromium@526857 445.768 +- 9.90241 6 good chromium@526858 536.833 +- 7.33696 6 bad <-- chromium@526859 533.719 +- 4.71724 6 bad chromium@526861 527.0 +- 8.31739 6 bad chromium@526870 527.282 +- 4.43021 6 bad Please refer to the following doc on diagnosing blink_perf regressions: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.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 blink_perf.image_decoder More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8957937154386407056 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