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

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


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

android-nexus6

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

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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : total:500ms_window:renderer_eqt_max/browse_social/browse_social_tumblr_infinite_scroll

Revision             Result                  N
chromium@513751      748.785 +- 696.898      21      good
chromium@513820      823.998 +- 1075.0       21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.tumblr.infinite.scroll system_health.common_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Looks like something bad was reverted.