Issue metadata
Sign in to add a comment
|
3.3%-5.2% regression in thread_times.key_silk_cases at 485907:486005 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8973425584544006576
,
Jul 22 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Ken Rockot Commit : 474df01407e5d38c85364ae4d1709b8d9af16f16 Date : Wed Jul 12 13:28:56 2017 Subject: Mojo C++ Bindings: Lazy Serialization Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : thread_times.key_silk_cases Metric : thread_IO_cpu_time_per_frame/thread_IO_cpu_time_per_frame Change : 3.13% | 3.1878814116 -> 3.28782038682 Revision Result N chromium@485915 3.18788 +- 0.054924 6 good chromium@485929 3.16642 +- 0.0508184 6 good chromium@485934 3.14876 +- 0.0321753 6 good chromium@485935 3.26102 +- 0.0303853 6 bad <-- chromium@485936 3.2688 +- 0.0249826 6 bad chromium@485938 3.25495 +- 0.0742266 9 bad chromium@485960 3.26452 +- 0.0452183 6 bad chromium@486005 3.28782 +- 0.040175 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 thread_times.key_silk_cases More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8973425584544006576 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 21 2017