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

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


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

chromium-rel-win7-dual
chromium-rel-win7-x64-dual

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

=== 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_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : seek/tulip2.mp4_seek_cold
  Change       : 6.21% | 204.413333333 -> 217.107777778

Revision             Result                  N
chromium@495791      204.413 +- 21.2876      9      good
chromium@495800      200.208 +- 12.2001      9      good
chromium@495801      204.313 +- 18.8706      9      good
chromium@495802      214.666 +- 15.5906      9      bad       <--
chromium@495804      213.065 +- 9.60837      6      bad
chromium@495808      217.108 +- 19.9212      9      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests media.tough_video_cases

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

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


For feedback, file a bug with component Speed>Bisection