Issue metadata
Sign in to add a comment
|
3.7%-45.6% regression in blink_perf.bindings at 526760:526942 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 8 2018
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8957930807797890544
,
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_one_perf_bisect Benchmark : blink_perf.dom Metric : move-up-with-hidden-elements/move-up-with-hidden-elements Change : 27.10% | 4.93 -> 6.26583333333 Revision Result N chromium@526855 4.93 +- 0.304132 6 good chromium@526857 5.03583 +- 0.380398 6 good chromium@526858 6.2205 +- 0.47381 6 bad <-- chromium@526861 6.26017 +- 0.392926 6 bad chromium@526866 6.21933 +- 0.325885 6 bad chromium@526877 6.28067 +- 0.441499 6 bad chromium@526899 6.37183 +- 0.873295 6 bad chromium@526942 6.26583 +- 0.143565 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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.dom More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8957930807797890544 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