Issue metadata
Sign in to add a comment
|
2.7%-4850.9% regression in loading.desktop at 504628:504763 |
||||||||||||||||||||||
Issue description1000+ alerts in loading.desktop. Most likely the same underlying cause as 770726.
,
Oct 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8966830302700027152
,
Oct 2 2017
=== BISECT JOB RESULTS === Perf regression found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. Bisect Details Configuration: winx64ati_perf_bisect Benchmark : loading.desktop Metric : timeToFirstContentfulPaint_avg/warm/FlipKart Change : 5323.78% | 21.4061666727 -> 1161.02266667 Suspected Commit Range 8 commits in range https://chromium.googlesource.com/chromium/src/+log/2e8a148e6c387088004f188c1e5f66169d51a340..b64a18def16cc3dd0a034e39adedcdd092e718f4 Revision Result N chromium@504642 21.4062 +- 4.60928 6 good chromium@504664 20.7758 +- 4.03137 6 good chromium@504669 21.486 +- 5.87674 6 good chromium@504670 --- --- build failure chromium@504671 --- --- build failure chromium@504672 --- --- build failure chromium@504673 --- --- build failure chromium@504674 --- --- build failure chromium@504675 --- --- build failure chromium@504676 --- --- build failure chromium@504677 1206.88 +- 220.708 6 bad chromium@504686 1156.82 +- 188.39 6 bad chromium@504729 1161.02 +- 203.337 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/8966830302700027152 For feedback, file a bug with component Speed>Bisection
,
Oct 3 2017
,
Oct 3 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 2 2017