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

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


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

chromium-rel-win7-x64-dual
chromium-rel-win8-dual

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

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

Suspected Commit
  Author : Bruce Dawson
  Commit : 43b6c849b3c49f71261a71fcb40455d0e263c49d
  Date   : Mon Aug 28 01:12:50 2017
  Subject: Revert "Change default VC++ compiler from 2015 to 2017"

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : speedometer
  Metric       : jQuery-TodoMVC/jQuery-TodoMVC
  Change       : 5.13% | 1060.12483333 -> 1114.52441667

Revision             Result                  N
chromium@497682      1060.12 +- 12.1033      6      good
chromium@497683      1061.15 +- 29.6118      6      good
chromium@497684      1117.89 +- 15.7636      6      bad       <--
chromium@497685      1121.03 +- 17.5013      6      bad
chromium@497688      1124.71 +- 18.975       6      bad
chromium@497693      1114.52 +- 15.1567      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 speedometer

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8969831615544120256


For feedback, file a bug with component Speed>Bisection