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

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


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

chromium-rel-mac-retina

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/text_hover_05000_pixels_per_second

Revision             Result                     N
chromium@499210      0.429269 +- 0.0667804      21      good
chromium@499342      0.427244 +- 0.0859484      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.05000.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/8969257806185642176


For feedback, file a bug with component Speed>Bisection

Ref build moves too, bisect can't repro