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

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


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

chromium-rel-win10
chromium-rel-win7-gpu-intel

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

=== 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 : eaccacb6302f7b0ea235fd7d1ff3aa7eaf8b20ef
  Date   : Mon Sep 18 06:35:37 2017
  Subject: Revert "Make VS 2017 the default compiler on Windows"

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : rasterize_and_record_micro.top_25
  Metric       : rasterize_time/file___static_top_25_cnn.html
  Change       : 6.22% | 2.2975 -> 2.4405

Revision             Result                    N
chromium@502529      2.2975 +- 0.0165982       6      good
chromium@502533      2.30583 +- 0.0134474      6      good
chromium@502534      2.30867 +- 0.022701       6      good
chromium@502535      2.4355 +- 0.00809321      6      bad       <--
chromium@502537      2.4405 +- 0.0179304       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=file...static.top.25.cnn.html rasterize_and_record_micro.top_25

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

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


For feedback, file a bug with component Speed>Bisection

This is a *good* bug. This means that when we switch to VS 2017 permanently we should expect to see this as an improvement.

Closing as Wont Fix even though I sort of probably will when I switch us to VS 2017 permanently.

 Issue 766885  has been merged into this issue.

 Issue 768064  has been merged into this issue.