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

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


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

android-one

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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_raster_cpu_time_per_frame/http___jsfiddle.net_rF9Gh_7_show_

Revision             Result                  N
chromium@499652      2.82782 +- 2.11519      21      good
chromium@499765      2.89134 +- 2.10766      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.rF9Gh.7.show. thread_times.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/8968031377057296768


For feedback, file a bug with component Speed>Bisection

Not sure if this is real, the graph went from being bi-modal to stable.

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

Bisect unable to find culprit, this regression exists in stable. Ignoring.