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

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


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

android-nexus5X
chromium-rel-mac11-air
chromium-rel-mac12

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

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

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/canvas_90000_pixels_per_second

Revision             Result                   N
chromium@499657      1.37897 +- 0.474617      21      good
chromium@499748      1.35082 +- 0.309703      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=canvas.90000.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/8968751190262306656


For feedback, file a bug with component Speed>Bisection

Looks like a revert and not bisecting so closing as wontfix.