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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame

Revision             Result                  N
chromium@486025      5.86649 +- 1.21199      21      good
chromium@486144      5.7795 +- 0.875137      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests 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/8973806073717428912


For feedback, file a bug with component Speed>Bisection

this went back down.