Issue metadata
Sign in to add a comment
|
7.9% regression in loading.mobile at 512430:513091 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 8 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8963474226970896432
,
Nov 8 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Koji Ishii Commit : 811fe6a25ddee5065812bf50733de963e58832cb Date : Tue Oct 31 14:34:37 2017 Subject: Add CrashKey to LazyLineBreakIterator on Android Bisect Details Configuration: android_one_perf_bisect Benchmark : loading.mobile Metric : cpuTimeToFirstMeaningfulPaint_avg/Regular-3G/SlideShare Change : 12.39% | 872.738 -> 980.913166667 Revision Result N chromium@512429 872.738 +- 54.9493 6 good chromium@512760 869.757 +- 13.689 6 good chromium@512802 864.575 +- 26.1834 6 good chromium@512823 868.725 +- 57.1782 6 good chromium@512824 856.118 +- 33.0243 6 good chromium@512825 986.19 +- 11.2616 6 bad <-- chromium@512826 996.995 +- 37.0831 6 bad chromium@512828 988.486 +- 29.3109 6 bad chromium@512833 993.695 +- 45.1561 6 bad chromium@512843 993.809 +- 62.3796 6 bad chromium@512926 995.148 +- 22.8734 6 bad chromium@513091 980.913 +- 29.0215 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=SlideShare loading.mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8963474226970896432 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 8 2017