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

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


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

chromium-rel-win7-x64-dual

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

=== 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_x64_perf_bisect
  Benchmark    : performance_browser_tests
  Metric       : CastV2Performance_gpu_30fps_slowwifi_autothrottling/encode
  Change       : 4.57% | 1.80531333333 -> 1.88788766667

Revision             Result                    N
chromium@495800      1.80531 +- 0.0330266      6      good
chromium@495801      1.81784 +- 0.0491879      6      good
chromium@495802      1.8725 +- 0.0336303       6      bad       <--
chromium@495804      1.88488 +- 0.0459351      6      bad
chromium@495808      1.88789 +- 0.0332831      6      bad

To Run This Test
  .\src\out\Release_x64\performance_browser_tests.exe --test-launcher-print-test-stdio=always --enable-gpu

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

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


For feedback, file a bug with component Speed>Bisection