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

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


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

chromium-rel-mac11
chromium-rel-mac11-pro
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
win-high-dpi

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16e19d09f80000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/16e19d09f80000

Pinpoint results show a clear regression, but don't detect it.

Simon, any thoughts on how to get a bisect result out of this?

Looks like all of these were reassigned to  crbug.com/784206  which found a culprit, but before I saw that I kicked off a new bisect here: https://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_high_dpi_perf_bisect/builds/852 on a metric that looked a bit cleaner.