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

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


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

android-nexus5

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : smoothness.key_silk_cases
  Metric       : avg_surface_fps/http___jsfiddle.net_3yDKh_16_show_

Revision             Result                  N
chromium@498864      58.8571 +- 1.60357      21      good
chromium@498919      58.9048 +- 1.9518       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/8969253098785814160


For feedback, file a bug with component Speed>Bisection

The ref changes similarly at the same time.