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

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


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

win-high-dpi

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Nico Weber
  Commit : 7cd2f6bd73c6a9c6200704e995b18ebb3168ead6
  Date   : Sat Aug 19 04:23:54 2017
  Subject: win: Turn off clang-by-default again for now.

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : startup.cold.blank_page
  Metric       : window_display_time/window_display_time
  Change       : 3.17% | 358.666666667 -> 347.285714286

Revision             Result                  N
chromium@495726      358.667 +- 471.774      21      good
chromium@495766      321.111 +- 53.5993      9       good
chromium@495786      321.333 +- 47.3498      9       good
chromium@495796      326.889 +- 35.7895      9       good
chromium@495801      326.444 +- 37.1244      9       good
chromium@495802      355.5 +- 38.4903        6       bad       <--
chromium@495803      349.111 +- 30.412       9       bad
chromium@495805      347.286 +- 55.8288      14      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 startup.cold.blank_page

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

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


For feedback, file a bug with component Speed>Bisection