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

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


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

chromium-rel-win7-gpu-nvidia

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

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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-scavenger_sum/browse_news/browse_news_cnn

Revision             Result                  N
chromium@502894      131.629 +- 38.4357      21      good
chromium@502979      134.714 +- 34.2905      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.cnn v8.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection