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

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


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

android-nexus5X
android-nexus6
android-nexus7v2
android-one
android-webview-nexus6
chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-air
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-mac12-mini-8gb
chromium-rel-win7-gpu-ati
win-high-dpi

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Sunny Sachanandani
  Commit : 2eb3c8ac7ffc6840dc07f5e8312576e107eece23
  Date   : Wed Sep 06 02:01:21 2017
  Subject: cc: Flush after every tile task set completes.

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/text_constant_full_page_raster_30000_pixels_per_second
  Change       : 69.01% | 1.39377350623 -> 2.35561427501

Revision             Result                   N
chromium@499724      1.39377 +- 0.218077      6      good
chromium@499785      1.37267 +- 0.294145      6      good
chromium@499816      1.48532 +- 0.288019      6      good
chromium@499831      1.39648 +- 0.316993      6      good
chromium@499839      1.47359 +- 0.258873      6      good
chromium@499843      1.40025 +- 0.370875      6      good
chromium@499844      1.43783 +- 0.34749       6      good
chromium@499845      2.47828 +- 0.287424      6      bad       <--
chromium@499846      2.35561 +- 0.218285      6      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 --story-filter=text.constant.full.page.raster.30000.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/8969082352392807792


For feedback, file a bug with component Speed>Bisection