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

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


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

chromium-rel-mac-retina
chromium-rel-mac11-pro
chromium-rel-win10
chromium-rel-win7-dual
win-high-dpi

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

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

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

Revision             Result                  N
chromium@514216      313.647 +- 292.243      21      good
chromium@514317      294.853 +- 288.916      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=REI loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

These all came back down again.