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

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


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

linux-release

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

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : V8-Only:duration_avg/browse_news/browse_news_hackernews

Revision             Result                  N
chromium@487410      920.242 +- 926.177      21      good
chromium@487550      915.091 +- 891.098      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.hackernews 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/8973205593378859104


For feedback, file a bug with component Speed>Bisection