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

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


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

chromium-rel-win7-gpu-intel

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

=== 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: winx64intel_perf_bisect
  Benchmark    : blink_perf.dom
  Metric       : select-single-remove/select-single-remove
  Change       : 17.84% | 280.481871148 -> 230.456194678

Revision             Result                  N
chromium@510764      280.482 +- 8.01161      6      good
chromium@510794      277.521 +- 3.10733      6      good
chromium@510809      279.769 +- 9.91112      6      good
chromium@510817      267.961 +- 40.2801      6      good
chromium@510821      283.475 +- 7.67782      6      good
chromium@510823      277.63 +- 16.3687       6      good
chromium@510824      230.456 +- 6.23376      6      bad       <--

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

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 blink_perf.dom

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

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


For feedback, file a bug with component Speed>Bisection