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

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


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

chromium-rel-win7-dual
chromium-rel-win7-x64-dual
Alerts fired for ranges overlapping the given range:
  https://chromeperf.appspot.com/group_report?rev_one=510777&rev_two=510909

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

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

Suspected Commit
  Author : Hans Wennborg
  Commit : 22525134c75ca2a005997a717f6887a23af86210
  Date   : Mon Oct 23 17:10:25 2017
  Subject: win: Re-enable Clang by default

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : seek/tulip2.vp9.webm_seek_cold
  Change       : 2.45% | 962.138333333 -> 985.74

Revision             Result                  N
chromium@510776      962.138 +- 8.51352      6      good
chromium@510814      957.468 +- 17.0963      6      good
chromium@510819      958.264 +- 14.3476      6      good
chromium@510822      963.243 +- 24.6325      6      good
chromium@510823      956.476 +- 7.00661      6      good
chromium@510824      995.0 +- 14.8204        6      bad       <--
chromium@510833      987.914 +- 18.7914      6      bad
chromium@510851      985.74 +- 8.47105       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --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/8964741963856532128


For feedback, file a bug with component Speed>Bisection