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

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


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

chromium-rel-mac11-pro

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

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

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/text_hover_60000_pixels_per_second

Revision             Result                  N
chromium@498729      25.4138 +- 9.60219      21      good
chromium@498773      24.8657 +- 10.4617      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=text.hover.60000.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/8969252917677413760


For feedback, file a bug with component Speed>Bisection

This recovered.