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

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


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

chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
linux-release

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

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-incremental-step_max/browse_news/browse_news_reddit

Revision             Result                 N
chromium@485896      3.10729 +- 4.7715      21      good
chromium@486045      3.2579 +- 3.80295      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.reddit 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/8973651606394964080


For feedback, file a bug with component Speed>Bisection

Not really actionable. A lot of the graphs also recovered.