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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : v8.detached_context_age_in_gc
  Metric       : V8_DetachedContextAgeInGC/https___www.google.com__hl_en_q_barack+obama

Revision             Result                  N
chromium@501719      3.38095 +- 2.99205      21      good
chromium@501822      3.52381 +- 3.03942      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=https...www.google.com..hl.en.q.barack.obama v8.detached_context_age_in_gc

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

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


For feedback, file a bug with component Speed>Bisection