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

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


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

chromium-rel-mac-retina

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/text_constant_full_page_raster_75000_pixels_per_second

Revision             Result                  N
chromium@497650      19.7846 +- 8.34411      21      good
chromium@497660      19.9986 +- 11.4194      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.constant.full.page.raster.75000.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/8969999963618446336


For feedback, file a bug with component Speed>Bisection

This recovered.