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

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


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

chromium-rel-win8-dual

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

=== 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_8_perf_bisect
  Benchmark    : jetstream
  Metric       : Score/Score
  Change       : 1.24% | 144.285714286 -> 145.952380952

Revision             Result                  N
chromium@510776      144.286 +- 4.44365      14      good
chromium@510813      144.571 +- 1.72746      14      good
chromium@510822      144.63 +- 0.737028      9       good
chromium@510823      144.556 +- 2.78887      9       good
chromium@510824      145.852 +- 3.43547      9       bad       <--
chromium@510825      145.815 +- 3.16618      9       bad
chromium@510827      145.667 +- 3.68179      9       bad
chromium@510831      145.667 +- 2.26078      9       bad
chromium@510849      145.952 +- 4.44365      14      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 jetstream

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

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


For feedback, file a bug with component Speed>Bisection