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

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


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

android-nexus5

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

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

Hi bokan@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 : David Bokan
  Commit : b0d47f5f4d4b9717bfdd43ae6d40257235d0848f
  Date   : Fri Oct 13 16:49:07 2017
  Subject: Fix coordinate space issues in scroll.js

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/text_20000_pixels_per_second
  Change       : 13.44% | 7.21581534861 -> 8.18551747291

Revision                                 Result                   N
chromium@508719                          7.21582 +- 0.230003      6      good
chromium@508786                          7.30855 +- 0.112696      6      good
chromium@508789                          7.30139 +- 0.215748      6      good
chromium@508789,catapult@b0d47f5f4d      8.26186 +- 0.291858      6      bad       <--
chromium@508789,catapult@dd5b39ac0c      8.16784 +- 0.23463       6      bad
chromium@508790                          8.33951 +- 0.263316      6      bad
chromium@508791                          8.31915 +- 0.200547      6      bad
chromium@508795                          8.2648 +- 0.368315       6      bad
chromium@508803                          8.18923 +- 0.122025      6      bad
chromium@508819                          8.28614 +- 0.272462      6      bad
chromium@508852                          8.18552 +- 0.183363      6      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=text.20000.pixels.per.second thread_times.tough_scrolling_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8965555340595272016


For feedback, file a bug with component Speed>Bisection

this is undoing an "improvement" that comes from https://chromium-review.googlesource.com/668376. That CL fixes gestures when pinch-zoomed so it changed what gestures are produced and affects performance on various runs (some better, some worse) but it shouldn't have affected this particular metric. The blamed CL fixes the issue so it's back to the original metric.

 Issue 775950  has been merged into this issue.

 Issue 776752  has been merged into this issue.

 Issue 776753  has been merged into this issue.

 Issue 776750  has been merged into this issue.