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

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


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

chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/text_constant_full_page_raster_15000_pixels_per_second

Revision             Result                   N
chromium@510849      2.79008 +- 0.203037      21      good
chromium@510942      2.81336 +- 0.202746      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/8964676620108116528


For feedback, file a bug with component Speed>Bisection

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14cba763040000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12d7d5f3040000

Running a few more bisects on a wider range, since this ramps up over a few CLs.

WontFix-ing since the pinpoint jobs saw a ton of noise.