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

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


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

android-nexus5X
android-webview-nexus5X
chromium-rel-win10

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

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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : Parse:duration_avg/browse_news/browse_news_flipboard

Revision             Result                  N
chromium@500588      130.496 +- 138.186      21      good
chromium@500632      152.315 +- 129.488      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.flipboard 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/8968763135091751248


For feedback, file a bug with component Speed>Bisection