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

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


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

chromium-rel-win7-dual

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

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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/text_constant_full_page_raster_15000_pixels_per_second

Revision             Result                  N
chromium@509929      58.2858 +- 6.68565      21      good
chromium@510017      58.1797 +- 5.60487      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.15000.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/8964186723327328736


For feedback, file a bug with component Speed>Bisection

This is within the noise.