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

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


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

chromium-rel-win7-gpu-nvidia

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

=== 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 : d7af1e3aba05d9839ecffa52585b6e4808212142
  Date   : Sat Sep 23 00:35:11 2017
  Subject: Make VS 2017 the default compiler on Windows

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : media_perftests
  Metric       : sinc_resampler_convolve/unoptimized_aligned
  Change       : 11.89% | 39397.5164107 -> 34617.5486607

Revision             Result                  N
chromium@503834      39397.5 +- 2234.37      9      good
chromium@503878      38186.0 +- 11966.5      9      good
chromium@503901      39563.5 +- 145.243      6      good
chromium@503912      39602.1 +- 94.4275      6      good
chromium@503914      39543.5 +- 503.127      6      good
chromium@503915      34622.7 +- 135.204      6      bad       <--
chromium@503918      34636.2 +- 91.5751      6      bad
chromium@503923      34617.5 +- 284.338      9      bad

To Run This Test
  .\src\out\Release_x64\media_perftests.exe --single-process-tests

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

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


For feedback, file a bug with component Speed>Bisection