Issue metadata
Sign in to add a comment
|
10.1%-25.4% regression in blink_perf.layout at 488907:488947 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 27 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8972961283033618016
,
Jul 27 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Naina Raisinghani Commit : fd7f99c9125b7f9b054b3a32c0100b526792f74c Date : Mon Jul 24 05:21:35 2017 Subject: Remove code and tests using StyleSharing Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : blink_perf.shadow_dom Metric : v1-large-shallow-layout/v1-large-shallow-layout Change : 19.99% | 83.7445 -> 100.482 Revision Result N chromium@488906 83.7445 +- 1.15038 6 good chromium@488914 86.098 +- 5.79137 6 good chromium@488915 103.4 +- 3.15046 6 bad <-- chromium@488916 105.795 +- 7.01841 6 bad chromium@488918 103.07 +- 2.86851 6 bad chromium@488921 103.701 +- 7.17096 6 bad chromium@488935 100.482 +- 3.00346 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 blink_perf.shadow_dom More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8972961283033618016 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 27 2017