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

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


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

chromium-rel-win8-dual

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : media_perftests
  Metric       : clockless_playback/sfx-flac.mp4

Revision             Result                  N
chromium@495267      7081.38 +- 3282.89      21      good
chromium@495384      7023.08 +- 3741.31      21      bad

To Run This Test
  .\src\out\Release\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/8970267265830438432


For feedback, file a bug with component Speed>Bisection

I somehow created two bugs for this regression...

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

Re-opening this one, closing the other duplicate. the association of graphs in chromeperf seems stuck on this bug rather than the ordinal. 

Comment 5 is a new bisect with wider range. 

 Issue 759106  has been merged into this issue.

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

Suspected Commit
  Author : Nico Weber
  Commit : 7cd2f6bd73c6a9c6200704e995b18ebb3168ead6
  Date   : Sat Aug 19 04:23:54 2017
  Subject: win: Turn off clang-by-default again for now.

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : media_perftests
  Metric       : clockless_playback/sfx-flac.mp4
  Change       : 54.98% | 9350.32959349 -> 4209.19613781

Revision             Result                  N
chromium@494141      9350.33 +- 2612.68      6      good
chromium@494990      8186.77 +- 1341.46      6      good
chromium@495414      7060.38 +- 1975.73      6      good
chromium@495626      6715.42 +- 1177.37      6      good
chromium@495732      7917.37 +- 1994.04      6      good
chromium@495785      6454.27 +- 2228.52      6      good
chromium@495799      6431.46 +- 1699.84      6      good
chromium@495801      7503.51 +- 1944.14      6      good
chromium@495802      4072.98 +- 583.797      6      bad       <--
chromium@495805      4615.89 +- 642.363      6      bad
chromium@495812      4090.28 +- 677.429      6      bad
chromium@495838      4209.2 +- 663.734       6      bad

To Run This Test
  .\src\out\Release\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/8970248161681531344


For feedback, file a bug with component Speed>Bisection