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

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


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

chromium-rel-win7-gpu-intel

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

=== Auto-CCing suspected CL author brucedawson@chromium.org ===

Hi brucedawson@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Bruce Dawson
  Commit : 8e6e8c57c1c30caf7e2756e95d5a59e90336b0bd
  Date   : Mon Jul 17 16:39:20 2017
  Subject: Revert "Test changing default Windows compiler to VS2017"

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/thread_raster_cpu_time_per_frame
  Change       : 9.72% | 1.61741225972 -> 1.77455002786

Revision             Result                    N
chromium@487044      1.61741 +- 0.0229877      6      good
chromium@487082      1.66309 +- 0.0136591      6      good
chromium@487101      1.65282 +- 0.0174096      6      good
chromium@487110      1.64763 +- 0.022662       6      good
chromium@487111      1.78511 +- 0.0271584      6      bad       <--
chromium@487112      1.78103 +- 0.0191965      6      bad
chromium@487113      1.81637 +- 0.0249658      6      bad
chromium@487115      1.81029 +- 0.014033       6      bad
chromium@487119      1.77455 +- 0.0184288      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 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/8973652118373700352


For feedback, file a bug with component Speed>Bisection

This bug means that VC++ 2017 gave a nice speed improvement on this benchmark which went away after the VC++ 2017 test was reverted. Therefore this isn't really a regression, it just means that we got a brief sample of a nice improvement. Closing as Wont Fix.