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

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


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

win-high-dpi

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

=== 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.parser
  Metric       : query-selector-id-deep/query-selector-id-deep
  Change       : 23.66% | 66062.1010968 -> 50429.0564662

Revision             Result                  N
chromium@510782      66062.1 +- 5465.28      6      good
chromium@510808      66431.0 +- 681.007      6      good
chromium@510821      66759.4 +- 3723.56      6      good
chromium@510823      67029.8 +- 889.659      6      good
chromium@510824      51733.3 +- 768.203      6      bad       <--
chromium@510827      50718.9 +- 4505.44      6      bad
chromium@510833      51237.9 +- 1906.13      6      bad
chromium@510884      50429.1 +- 444.319      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.parser

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

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


For feedback, file a bug with component Speed>Bisection