Issue metadata
Sign in to add a comment
|
17.8% regression in page_cycler_v2.intl_es_fr_pt-BR at 471259:471298 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 18 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979248331293506240
,
May 18 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64_high_dpi_perf_bisect Benchmark : page_cycler_v2.intl_es_fr_pt-BR Metric : timeToFirstContentfulPaint_avg/pcv1-warm/http___www.orange.fr_ Revision Result N chromium@471258 70.5727 +- 20.2319 21 good chromium@471298 70.7281 +- 29.5352 21 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=http...www.orange.fr. page_cycler_v2.intl_es_fr_pt-BR Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979248331293506240 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5212981178138624 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
May 18 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979239068287079072
,
May 18 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64_high_dpi_perf_bisect Benchmark : page_cycler_v2.intl_es_fr_pt-BR Metric : timeToFirstContentfulPaint_avg/pcv1-warm/http___www.orange.fr_ Revision Result N chromium@471258 70.9146 +- 23.3879 21 good chromium@471298 72.0862 +- 34.2224 21 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=http...www.orange.fr. page_cycler_v2.intl_es_fr_pt-BR Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979239068287079072 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5212981178138624 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
May 19 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979165908305877936
,
May 19 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64_high_dpi_perf_bisect Benchmark : page_cycler_v2.intl_es_fr_pt-BR Metric : timeToFirstMeaningfulPaint_avg/pcv1-cold/http___www.ebay.es_sch_i.html?_sacat_382__trkparms_clkid%3D6548971389060485883__qi_RTM1381637 Revision Result N chromium@471258 891.154 +- 131.031 21 good chromium@471298 891.577 +- 71.1036 21 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=http...www.ebay.es.sch.i.html..sacat.382..trkparms.clkid.3D6548971389060485883..qi.RTM1381637 page_cycler_v2.intl_es_fr_pt-BR Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979165908305877936 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5772828084797440 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
May 19 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979159793458874144
,
May 19 2017
=== Auto-CCing suspected CL author bashi@chromium.org === Hi bashi@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : bashi Commit : c5106fdfb45ca1c85f5018dfbf0989d3c97db323 Date : Fri May 12 09:38:32 2017 Subject: memory coordinator: Introduce MemoryCoordinatorImpl::Policy Bisect Details Configuration: winx64_high_dpi_perf_bisect Benchmark : page_cycler_v2.intl_es_fr_pt-BR Metric : timeToFirstMeaningfulPaint_avg/pcv1-cold/http___www.ebay.es_sch_i.html?_sacat_382__trkparms_clkid%3D6548971389060485883__qi_RTM1381637 Change : 3.74% | 931.961928574 -> 897.082285714 Revision Result N chromium@471258 931.962 +- 198.048 14 good chromium@471259 939.101 +- 187.054 14 good chromium@471260 889.958 +- 29.1517 9 bad <-- chromium@471261 893.353 +- 119.958 21 bad chromium@471263 901.447 +- 89.4201 14 bad chromium@471268 902.728 +- 88.5844 9 bad chromium@471278 888.215 +- 37.0265 6 bad chromium@471298 897.082 +- 45.6223 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=http...www.ebay.es.sch.i.html..sacat.382..trkparms.clkid.3D6548971389060485883..qi.RTM1381637 page_cycler_v2.intl_es_fr_pt-BR Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979159793458874144 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5772828084797440 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
May 19 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979146662468444848
,
May 19 2017
Something is weird here, the bisect actually found in *improvement* from bashi's change. I kicked off a bisect on a different bot.
,
May 19 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64ati_perf_bisect Benchmark : page_cycler_v2.intl_ko_th_vi Metric : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___kenh14.vn_home.chn Revision Result N chromium@471247 401.373 +- 51.4678 21 good chromium@471290 416.507 +- 374.745 21 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=http...kenh14.vn.home.chn page_cycler_v2.intl_ko_th_vi Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979146662468444848 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5340330246799360 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
May 19 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979140918234991792
,
May 19 2017
Issue 724266 has been merged into this issue.
,
May 19 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64ati_perf_bisect Benchmark : page_cycler_v2.intl_ko_th_vi Metric : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___kenh14.vn_home.chn Revision Result N chromium@471247 424.302 +- 423.764 21 good chromium@471290 403.415 +- 36.4033 21 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=http...kenh14.vn.home.chn page_cycler_v2.intl_ko_th_vi Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979140918234991792 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5340330246799360 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Jul 27 2017
This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by tdres...@chromium.org
, May 18 2017