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

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


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

android-nexus5X

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

=== 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_xLuvC_1_show_

Revision             Result                  N
chromium@520436      29.9555 +- 2.60906      21      good
chromium@520470      29.8682 +- 4.27317      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.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/8961032703060400224


For feedback, file a bug with component Speed>Bisection

bimodal, just returning to a previous level