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

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


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

win-high-dpi

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

=== 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    : dromaeo.domcorequery
  Metric       : dom/dom
  Change       : 14.82% | 24906.5452829 -> 21214.3626385

Revision             Result                  N
chromium@510782      24906.5 +- 809.323      6      good
chromium@510808      24198.7 +- 1620.27      6      good
chromium@510821      24531.7 +- 452.736      6      good
chromium@510823      23174.9 +- 1050.1       6      good
chromium@510824      21185.8 +- 91.5166      6      bad       <--
chromium@510827      21109.8 +- 303.781      6      bad
chromium@510833      20999.0 +- 284.685      6      bad
chromium@510884      21214.4 +- 320.324      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 dromaeo.domcorequery

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

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


For feedback, file a bug with component Speed>Bisection