Issue metadata
Sign in to add a comment
|
106.8% regression in smoothness.sync_scroll.key_mobile_sites_smooth at 455090:455183 |
||||||||||||||||||||
Issue descriptionBisect to follow
,
Mar 8 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8985656333331831296
,
Mar 8 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8985656313879163552
,
Mar 8 2017
=== Auto-CCing suspected CL author pdr@chromium.org === Hi pdr@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 : pdr Commit : a20ad732333dc9db2b545886acd16a11abdc5842 Date : Tue Mar 07 17:11:15 2017 Subject: Remove indirection: setup scrollbar scroll layers in the scrollbar constructor Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : smoothness.sync_scroll.key_mobile_sites_smooth Metric : first_gesture_scroll_update_latency/http___mlb.com_ Change : 76.94% | 11.6092857143 -> 19.6928571429 Revision Result N chromium@455089 11.6093 +- 2.67259 14 good chromium@455101 12.602 +- 4.33947 14 good chromium@455104 11.37 +- 1.27654 9 good chromium@455105 22.0138 +- 11.076 6 bad <-- chromium@455106 19.9673 +- 17.2486 9 bad chromium@455107 29.5067 +- 16.7942 6 bad chromium@455113 21.3167 +- 14.8627 9 bad chromium@455136 19.9255 +- 34.6235 21 bad chromium@455183 19.6929 +- 20.3684 14 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...mlb.com. smoothness.sync_scroll.key_mobile_sites_smooth Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8985656333331831296 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5057214110236672 | 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!
,
Mar 8 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: android_nexus5_perf_bisect Benchmark : smoothness.sync_scroll.key_mobile_sites_smooth Metric : first_gesture_scroll_update_latency/http___mlb.com_ Change : 23.48% | 15.4671428571 -> 19.0989047619 Suspected Commit Range 2 commits in range https://chromium.googlesource.com/chromium/src/+log/2e97347bcd54763ed7e4b3a692537bd8304975d7..a11672fb4c998040224d7dc97e5bdc05d46a4145 Revision Result N chromium@455052 15.4671 +- 77.9166 21 good chromium@455085 11.7953 +- 2.42126 9 good chromium@455102 11.7099 +- 2.38706 9 good chromium@455104 11.4595 +- 2.21775 14 good chromium@455105 --- --- build failure chromium@455106 22.1994 +- 37.4896 14 bad chromium@455110 24.375 +- 2.80111 6 bad chromium@455118 21.9024 +- 21.0112 14 bad chromium@455183 19.0989 +- 35.7864 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...mlb.com. smoothness.sync_scroll.key_mobile_sites_smooth Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8985656313879163552 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4975051520081920 | 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!
,
Mar 9 2017
,
Apr 12 2017
These were temporary progressions and have returned to baseline. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by benhenry@google.com
, Mar 8 2017