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

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


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

chromium-rel-win7-gpu-nvidia
chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-total_avg/browse_news/browse_news_nytimes

Revision             Result                  N
chromium@503620      1.62735 +- 1.71465      21      good
chromium@503666      1.64547 +- 1.47216      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.nytimes 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/8967136521589568112


For feedback, file a bug with component Speed>Bisection

v8-gc_total_avg is not actionable.