Issue metadata
Sign in to add a comment
|
1.2%-28.3% regression in performance_browser_tests at 485333:485476 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974256450868864240
,
Jul 12 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Justin Novosad Commit : 3750a7881ce851e03ce6177dca30307eb4a7f5c6 Date : Mon Jul 10 20:50:59 2017 Subject: Disabling display list 2D canvas by default Bisect Details Configuration: winx64intel_perf_bisect Benchmark : performance_browser_tests Metric : TabCapturePerformance_comp_gpu/Capture Change : 27.87% | 18.3474011667 -> 23.4615095 Revision Result N chromium@485332 18.3474 +- 0.18344 6 good chromium@485362 18.4317 +- 0.202803 6 good chromium@485370 18.4367 +- 0.221102 6 good chromium@485371 23.4776 +- 0.250591 6 bad <-- chromium@485372 23.5155 +- 0.284293 6 bad chromium@485374 23.444 +- 0.165261 6 bad chromium@485377 23.4281 +- 0.190608 6 bad chromium@485392 23.468 +- 0.165241 6 bad chromium@485452 23.4615 +- 0.349665 6 bad To Run This Test .\src\out\Release_x64\performance_browser_tests.exe --test-launcher-print-test-stdio=always --enable-gpu More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8974256450868864240 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