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

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


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

android-nexus5

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : smoothness.key_silk_cases
  Metric       : mean_frame_time/http___jsfiddle.net_xLuvC_1_show_


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=http...jsfiddle.net.xLuvC.1.show. smoothness.key_silk_cases

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

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


For feedback, file a bug with component Speed>Bisection

There was a big improvement after these regressions.