Issue metadata
Sign in to add a comment
|
96.3%-99.4% regression in blink_perf.canvas at 493986:493992 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8971155032178564560
,
Aug 16 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Xu Xing Commit : e3775832e557909d8c24243acb0a5296444a0ce0 Date : Sun Aug 13 04:02:52 2017 Subject: When being copied into another canvas, avoid to check if canvas is dirty Bisect Details Configuration: mac_10_11_perf_bisect Benchmark : blink_perf.canvas Metric : draw-static-webgl-to-hw-accelerated-canvas-2d/draw-static-webgl-to-hw-accelerated-canvas-2d Change : 96.29% | 102608.493726 -> 3803.058128 Revision Result N chromium@493985 102608 +- 10108.9 6 good chromium@493986 104916 +- 6604.28 6 good chromium@493987 3581.04 +- 216.863 6 bad <-- chromium@493988 3727.99 +- 319.937 6 bad chromium@493991 3803.06 +- 113.955 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.canvas More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8971155032178564560 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 15 2017