Issue metadata
Sign in to add a comment
|
18.5% regression in blink_perf.canvas at 483327:483388 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974256651424346000
,
Jul 12 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Kevin Bailey Commit : 3dc51db95f327e4f86962c94d6d5455ee75cf433 Date : Thu Jun 29 14:43:43 2017 Subject: [omnibox] Select all when we revert all Bisect Details Configuration: winx64nvidia_perf_bisect Benchmark : blink_perf.canvas Metric : putImageData/putImageData Change : 12.88% | 1068.23060037 -> 930.636600398 Revision Result N chromium@483326 1068.23 +- 356.814 14 good chromium@483357 1113.55 +- 60.754 6 good chromium@483361 1090.63 +- 53.2441 6 good chromium@483362 909.157 +- 53.2863 6 bad <-- chromium@483363 931.522 +- 83.2826 6 bad chromium@483365 930.965 +- 100.734 6 bad chromium@483373 902.301 +- 60.4846 6 bad chromium@483388 930.637 +- 206.037 9 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.canvas More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8974256651424346000 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 12 2017