Issue metadata
Sign in to add a comment
|
9.1%-30.8% regression in smoothness.top_25_smooth at 490015:490218 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 31 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8972538189104731376
,
Jul 31 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64intel_perf_bisect Benchmark : smoothness.top_25_smooth Metric : mean_input_event_latency/http___news.yahoo.com Revision Result N chromium@490067 15.6907 +- 14.6045 21 good chromium@490187 15.1359 +- 12.3819 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...news.yahoo.com smoothness.top_25_smooth More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8972538189104731376 For feedback, file a bug with component Speed>Bisection
,
Aug 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970613317057334752
,
Aug 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970613294629326800
,
Aug 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970613275223977984
,
Aug 21 2017
Kicked off a few more bisects.
,
Aug 21 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Khushal Commit : ca2c1cf2d9748d25050bfe7f71ee40463588a6a9 Date : Thu Jul 27 23:06:43 2017 Subject: cc: Split pending tree duration metrics based on main/impl side tree. Bisect Details Configuration: win_x64_perf_bisect Benchmark : smoothness.top_25_smooth Metric : frame_times/https___www.google.com_search?q_cats_tbm_isch Change : 11.70% | 17.9281270034 -> 20.0260509979 Revision Result N chromium@490056 17.9281 +- 2.35654 6 good chromium@490062 17.3752 +- 1.0944 6 good chromium@490063 20.064 +- 0.405906 6 bad <-- chromium@490064 20.1792 +- 0.297931 6 bad chromium@490065 20.0412 +- 0.338072 6 bad chromium@490067 19.992 +- 0.584594 6 bad chromium@490077 20.073 +- 0.131882 6 bad chromium@490097 20.043 +- 0.341177 6 bad chromium@490137 20.0516 +- 0.240352 6 bad chromium@490218 20.0261 +- 0.337783 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=https...www.google.com.search.q.cats.tbm.isch smoothness.top_25_smooth More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8970613317057334752 For feedback, file a bug with component Speed>Bisection
,
Aug 22 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Khushal Commit : ca2c1cf2d9748d25050bfe7f71ee40463588a6a9 Date : Thu Jul 27 23:06:43 2017 Subject: cc: Split pending tree duration metrics based on main/impl side tree. Bisect Details Configuration: win_x64_perf_bisect Benchmark : smoothness.top_25_smooth Metric : frame_times/https___www.google.com_search?q_cats_tbm_isch Change : 14.98% | 17.4953791299 -> 20.1157946926 Revision Result N chromium@490056 17.4954 +- 1.55257 6 good chromium@490062 17.0483 +- 1.06333 6 good chromium@490063 20.0757 +- 0.350988 6 bad <-- chromium@490064 20.216 +- 0.257546 6 bad chromium@490065 20.0921 +- 0.32974 6 bad chromium@490067 20.0461 +- 0.307534 6 bad chromium@490077 20.1185 +- 0.245631 6 bad chromium@490097 20.0513 +- 0.419022 6 bad chromium@490137 20.1319 +- 0.257408 6 bad chromium@490218 20.1158 +- 0.393945 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=https...www.google.com.search.q.cats.tbm.isch smoothness.top_25_smooth More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8970613294629326800 For feedback, file a bug with component Speed>Bisection
,
Aug 22 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: 099c1190811a71b20162df04a53368b3d2a7f0ef bad_revision : e735d5fc13caaa2fe9b188cfc86a4fe62e6eee81 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: winx64nvidia_perf_bisect Benchmark : smoothness.tough_animation_cases Metric : frame_times/frame_times Revision Result N chromium@489914 18.5711 +- 0.0529675 6 good chromium@490073 18.5844 +- 0.0269676 6 good chromium@490152 18.5905 +- 0.0285558 6 good chromium@490192 18.655 +- 0.105082 6 good chromium@490212 18.7613 +- 0.0576561 6 bad chromium@490231 18.7484 +- 0.0327284 6 bad chromium@490547 18.7969 +- 0.0503042 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 smoothness.tough_animation_cases More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8970613275223977984 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 31 2017