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

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


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

linux-release
win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-incremental-step_sum/browse_media/browse_media_flickr_infinite_scroll

Revision             Result                  N
chromium@504117      103.951 +- 121.424      17      good
chromium@504228      111.254 +- 91.0163      20      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.flickr.infinite.scroll 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/8967136624686536976


For feedback, file a bug with component Speed>Bisection