Issue metadata
Sign in to add a comment
|
7.5% improvement in speedometer at 518746:518863 |
||||||||||||||||||||||
Issue descriptionDocumenting improvement.
,
Jan 12 2018
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8957600624495668160
,
Jan 12 2018
=== Auto-CCing suspected CL author lfg@chromium.org === Hi lfg@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Lucas Furukawa Gadani Commit : b9fddd03657a4b15506833bf7678a51785094dc7 Date : Wed Nov 22 22:55:17 2017 Subject: Optimize HTML parser for speed instead of size on Android. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : speedometer Metric : jQuery-TodoMVC/jQuery-TodoMVC Change : 6.74% | 10571.3505556 -> 9858.54333333 Revision Result N chromium@518745 10571.4 +- 132.138 6 good chromium@518772 10486.5 +- 38.375 6 good chromium@518779 10466.5 +- 111.868 6 good chromium@518780 10524.8 +- 218.338 6 good chromium@518781 9918.52 +- 71.0468 6 bad <-- chromium@518782 9939.27 +- 171.47 6 bad chromium@518785 9924.35 +- 179.241 6 bad chromium@518798 9809.1 +- 162.847 6 bad chromium@518863 9858.54 +- 172.553 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 speedometer More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8957600624495668160 For feedback, file a bug with component Speed>Bisection
,
Jan 12 2018
Marking as fixed. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jan 12 2018