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

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


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

android-nexus5X
android-nexus6

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : smoothness.key_silk_cases
  Metric       : mean_frame_time/http___jsfiddle.net_3yDKh_16_show_

Revision             Result                   N
chromium@498936      16.8343 +- 0.163781      21      good
chromium@499053      16.8213 +- 0.169712      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=http...jsfiddle.net.3yDKh.16.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/8969255837635270880


For feedback, file a bug with component Speed>Bisection

This recovered.