All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=759573

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=131db3b3573c612a57be46b0328727b381ebb9d75f4eacc5e513fba594ccbbd1


Bot(s) for this bug's original alert(s):

chromium-rel-mac-retina

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970008290671901520

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : first_gesture_scroll_update_latency/http___news.yahoo.com

Revision             Result                  N
chromium@497584      12.2382 +- 31.1737      21      good
chromium@497650      14.2351 +- 33.7765      21      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=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/8970008290671901520


For feedback, file a bug with component Speed>Bisection

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8966194872542179408

Weird that bisect can't reproduce; trying a wider range on the other bot this happened on.

=== Auto-CCing suspected CL author sahel@chromium.org ===

Hi sahel@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 : Sahel Sharify
  Commit : f53825a1fb92e74b9a889b9501243e03de57094d
  Date   : Fri Aug 25 19:16:21 2017
  Subject: Wheel scroll latching and async wheel events flags enabled in testing config.

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : first_gesture_scroll_update_latency/https___www.google.com_search?q_cats_tbm_isch
  Change       : 187.99% | 4.71477777778 -> 13.5778888889

Revision             Result                   N
chromium@497381      4.71478 +- 0.274244      9       good
chromium@497451      4.565 +- 0.958569        9       good
chromium@497469      4.1945 +- 1.13781        6       good
chromium@497478      4.636 +- 0.509865        9       good
chromium@497482      4.09067 +- 1.34052       6       good
chromium@497483      16.7568 +- 9.52781       6       bad       <--
chromium@497484      13.9477 +- 13.5757       6       bad
chromium@497486      12.1664 +- 23.5993       14      bad
chromium@497520      15.1828 +- 16.5981       9       bad
chromium@497659      13.5779 +- 17.2547       9       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=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/8966194872542179408


For feedback, file a bug with component Speed>Bisection

sahel: Any update on this bug? This looks like a pretty big regression on smoothness benchmarks. Adding benchmark owner vmiura for guidance.

https://chromium-review.googlesource.com/849313 fixes the regression.
The numbers for smoothness.top_25_smooth/first_gesture_scroll_update_latency are back to what they used to be.