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

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


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

chromium-rel-win7-x64-dual
win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-scavenger_avg/browse_news/browse_news_flipboard

Revision             Result                   N
chromium@490681      2.50493 +- 1.22397       21      good
chromium@490683      2.47568 +- 0.796822      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.news.flipboard 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/8972265608300376240


For feedback, file a bug with component Speed>Bisection

Not reproducible.