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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghqbFpAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-sX2gwsM


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

chromium-rel-win10
chromium-rel-win7-gpu-ati

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

=== 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       : vector_math_ewma_and_max_power/unoptimized
  Change       : 1.24% | 50.0648463749 -> 49.4456306988

Revision             Result                    N
chromium@475131      50.0648 +- 0.0789713      6      good
chromium@475178      50.0818 +- 0.0371776      6      good
chromium@475202      50.0934 +- 0.0356849      6      good
chromium@475208      50.0464 +- 0.105824       6      good
chromium@475211      50.0955 +- 0.0384175      6      good
chromium@475212      49.5571 +- 0.0811663      6      bad       <--
chromium@475213      49.5794 +- 0.0257863      6      bad
chromium@475214      49.5439 +- 0.100769       6      bad
chromium@475225      49.4456 +- 0.302095       6      bad

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

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

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


| 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!