Issue metadata
Sign in to add a comment
|
1.5%-120% regression in loading.desktop at 484688:484870 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974260920908147312
,
Jul 12 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : rch Commit : d6e1cab1edf5f432d2ce09ff8ee34fe14abaff5a Date : Fri Jul 07 03:59:30 2017 Subject: Enable QUIC v39 by default. Bisect Details Configuration: winx64_high_dpi_perf_bisect Benchmark : loading.desktop Metric : timeToFirstContentfulPaint_avg/pcv1-warm/MLB Change : 54.33% | 705.627785716 -> 1178.96171429 Revision Result N chromium@484780 705.628 +- 1358.34 14 good chromium@484818 878.097 +- 1752.78 21 good chromium@484823 832.63 +- 920.003 9 good chromium@484825 618.728 +- 718.222 6 good chromium@484826 1279.82 +- 514.81 9 bad <-- chromium@484828 1322.54 +- 211.271 9 bad chromium@484837 1287.38 +- 650.262 9 bad chromium@484855 1178.96 +- 839.469 14 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 --story-filter=MLB loading.desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8974260920908147312 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