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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghuSVsgoM


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

chromium-rel-win10

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

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

Suspected Commit
  Author : sebmarchand
  Commit : 833aa96095e1f827ffc05af8bf545a094ffa6e35
  Date   : Sat May 27 01:34:31 2017
  Subject: Changing default Windows compiler to VS2017

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : media_perftests
  Metric       : sinc_resampler_convolve/unoptimized_aligned
  Change       : 13.01% | 36350.2224114 -> 31635.581545

Revision             Result                  N
chromium@475131      36350.2 +- 159.006      9      good
chromium@475178      35762.2 +- 5179.25      9      good
chromium@475202      36351.9 +- 136.112      6      good
chromium@475208      36378.9 +- 27.0673      6      good
chromium@475211      35954.6 +- 1559.46      6      good
chromium@475212      31617.7 +- 45.3801      6      bad       <--
chromium@475213      31616.7 +- 63.9671      6      bad
chromium@475214      31620.3 +- 52.4117      6      bad
chromium@475225      31635.6 +- 63.7575      9      bad

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

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8978150674271225584

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5211969000308736


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!