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

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


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

win-high-dpi

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : blink_perf.dom
  Metric       : select-multiple-add/select-multiple-add
  Change       : 4.45% | 3214.02941973 -> 3357.12813565

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/750ba7027d0a8d62aa843a0d27c2f13365022ca8..2e9451814cc0329083e6a3eeac30cfb67ab75c46


Revision             Result                  N
chromium@510733      3214.03 +- 609.174      9        good
chromium@510758      3229.53 +- 719.899      9        good
chromium@510770      3330.06 +- 107.885      14       good
chromium@510777      3331.78 +- 109.327      14       good
chromium@510779      3316.21 +- 257.789      14       good
chromium@510780      ---                     ---      build failure
chromium@510781      ---                     ---      build failure
chromium@510782      3357.13 +- 45.727       14       bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

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 blink_perf.dom

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

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


For feedback, file a bug with component Speed>Bisection

Bisect didn't repro a large regression, and these are noisy/many recovered.