Issue metadata
Sign in to add a comment
|
4.6%-4362.5% regression in loading.desktop at 494019:494204 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8971096878749774656
,
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: win_8_perf_bisect Benchmark : loading.desktop Metric : timeToFirstContentfulPaint_avg/pcv1-warm/Yandex Change : 1880.10% | 75.6216666748 -> 1497.38333334 Revision Result N chromium@494045 75.6217 +- 204.004 6 good chromium@494046 37.6143 +- 8.57774 6 good chromium@494046,catapult@122dd5e91b 1701.44 +- 336.92 6 bad <-- chromium@494047 1664.92 +- 208.567 6 bad chromium@494048 1650.12 +- 180.323 6 bad chromium@494051 1682.06 +- 124.294 6 bad chromium@494057 1621.95 +- 294.163 6 bad chromium@494069 1699.36 +- 520.537 6 bad chromium@494093 1486.28 +- 114.714 6 bad chromium@494141 1497.38 +- 228.441 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 --story-filter=Yandex loading.desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8971096878749774656 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