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

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


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

chromium-rel-win7-dual
chromium-rel-win7-gpu-ati

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

=== 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_perf_bisect
  Benchmark    : blink_perf.parser
  Metric       : query-selector-last/query-selector-last
  Change       : 20.80% | 1333.11874498 -> 1055.79755272

Revision             Result                  N
chromium@497681      1333.12 +- 4.01777      6      good
chromium@497683      1330.76 +- 13.915       6      good
chromium@497684      1076.81 +- 8.67592      6      bad       <--
chromium@497685      1043.55 +- 19.4307      6      bad
chromium@497688      1042.03 +- 4.18086      6      bad
chromium@497694      1055.8 +- 6.01385       6      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 blink_perf.parser

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

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


For feedback, file a bug with component Speed>Bisection