Issue metadata
Sign in to add a comment
|
20%-5374.7% regression in loading.desktop at 494021:494119 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8971086360557787760
,
Aug 16 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : perezju Commit : 122dd5e91bf64888049459ce73a8fd34c084cfe0 Date : Mon Aug 14 12:28:51 2017 Subject: [Telemetry] Reuse shared state between story runs Bisect Details Configuration: winx64nvidia_perf_bisect Benchmark : loading.desktop Metric : timeToFirstContentfulPaint_avg/pcv1-warm/FlipKart Change : 4308.05% | 47.4696666698 -> 2092.48783335 Revision Result N chromium@494036 47.4697 +- 3.28358 6 good chromium@494043 47.1477 +- 7.94345 6 good chromium@494046 46.2173 +- 4.72913 6 good chromium@494046,catapult@122dd5e91b 2159.01 +- 159.75 6 bad <-- chromium@494047 2108.11 +- 257.154 6 bad chromium@494048 2146.13 +- 324.421 6 bad chromium@494049 2148.93 +- 272.866 6 bad chromium@494062 2126.47 +- 258.315 6 bad chromium@494087 2092.49 +- 254.995 6 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=FlipKart loading.desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8971086360557787760 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 16 2017