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

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


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

win-high-dpi

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

=== 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: winx64_high_dpi_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : get-elements-by-tag-name/get-elements-by-tag-name
  Change       : 18.76% | 384.711788137 -> 312.538881031

Revision             Result                  N
chromium@510782      384.712 +- 53.1286      6      good
chromium@510808      399.296 +- 6.24568      6      good
chromium@510821      394.881 +- 7.43104      6      good
chromium@510823      398.87 +- 12.3647       6      good
chromium@510824      313.19 +- 6.25993       6      bad       <--
chromium@510827      323.846 +- 19.4798      6      bad
chromium@510833      315.373 +- 30.9346      6      bad
chromium@510884      312.539 +- 3.50112      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.bindings

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

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


For feedback, file a bug with component Speed>Bisection