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

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


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

chromium-rel-win7-dual

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

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

=== 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_perf_bisect
  Benchmark    : speedometer
  Metric       : jQuery-TodoMVC/jQuery-TodoMVC
  Change       : 5.42% | 572.3335 -> 541.337083333

Revision             Result                  N
chromium@510820      572.334 +- 11.9746      6      good
chromium@510823      576.724 +- 7.15976      6      good
chromium@510824      530.523 +- 11.2153      6      bad       <--
chromium@510825      537.324 +- 11.5133      6      bad
chromium@510826      535.206 +- 17.9158      6      bad
chromium@510832      540.055 +- 11.6783      6      bad
chromium@510843      532.141 +- 16.1575      6      bad
chromium@510865      550.193 +- 3.65051      6      bad
chromium@510909      541.337 +- 13.5445      6      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 speedometer

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

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


For feedback, file a bug with component Speed>Bisection

=== 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_perf_bisect
  Benchmark    : speedometer
  Metric       : jQuery-TodoMVC/jQuery-TodoMVC
  Change       : 4.51% | 570.530833333 -> 544.825111111

Revision             Result                  N
chromium@510820      570.531 +- 17.9945      9      good
chromium@510823      576.503 +- 29.3634      6      good
chromium@510824      533.379 +- 16.1332      6      bad       <--
chromium@510825      530.489 +- 10.4864      6      bad
chromium@510826      534.741 +- 19.73        6      bad
chromium@510832      529.686 +- 11.3001      6      bad
chromium@510843      540.608 +- 26.7912      6      bad
chromium@510865      529.566 +- 12.7833      6      bad
chromium@510909      544.825 +- 50.7881      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 speedometer

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

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


For feedback, file a bug with component Speed>Bisection

Wait, is this a regression or an improvement? The title says one thing, but the comments suggest the score dropped?