Issue metadata
Sign in to add a comment
|
18.1% regression in blink_perf.dom at 495051:495102 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 28 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8969998062112406832
,
Aug 29 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Dominic Mazzoni Commit : 91ce4a5c047cf0a01f7d23c839bd4364428fa6ad Date : Thu Aug 17 04:47:27 2017 Subject: Add use counters for all ARIA attributes. Bisect Details Configuration: mac_air_perf_bisect Benchmark : blink_perf.dom Metric : modify-element-title/modify-element-title Change : 16.34% | 112.7325 -> 131.1475 Revision Result N chromium@495050 112.733 +- 4.63443 6 good chromium@495063 112.673 +- 7.9262 6 good chromium@495070 110.917 +- 4.84664 6 good chromium@495073 116.183 +- 8.8405 6 good chromium@495075 112.328 +- 6.81076 6 good chromium@495076 127.013 +- 6.35784 6 bad <-- chromium@495102 131.148 +- 5.3758 6 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --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/8969998062112406832 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 28 2017