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

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


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

chromium-rel-win10
win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : Parse-Background:duration_avg/browse_media/browse_media_pinterest

Revision             Result                  N
chromium@508940      722.916 +- 353.726      21      good
chromium@508944      729.409 +- 331.149      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=browse.media.pinterest v8.runtimestats.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection

not reproducible, seems to be a bot issue