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

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


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

chromium-rel-mac12-mini-8gb

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

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

Bisect Details
  Configuration: mac_10_12_mini_8gb_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/canvas_50000_pixels_per_second

Revision             Result                  N
chromium@499602      10.969 +- 2.57519       21      good
chromium@499660      11.0299 +- 4.06071      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.50000.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/8968029900622678720


For feedback, file a bug with component Speed>Bisection

What ever made this metric super noisy went away.  We can close this.