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

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


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

win-high-dpi

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstMeaningfulPaint_avg/warm/24h

Revision             Result                  N
chromium@510782      710.734 +- 21.8233      21      good
chromium@510884      725.786 +- 122.306      21      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 --story-filter=24h loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

This recovered.