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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-warm/FarsNews

Revision             Result                  N
chromium@498039      220.819 +- 55.4454      21      good
chromium@498089      217.042 +- 46.5666      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=FarsNews loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14e2409b780000

Trying a bisect on a wider range.

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

Can't repro.