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

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


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

android-nexus5X

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_total_all_cpu_time_per_frame/http___jsfiddle.net_bNp2h_3_show_
  Change       : 1.95% | 23.8625476289 -> 23.3972189118

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/add7a2d66b19d47f5beac8cb09dcbc903800726d..2e9eaa6845ab922bbd6a94accbef6af3e7ea2074


Revision             Result                  N
chromium@494029      23.8625 +- 2.16624      21       good
chromium@494044      23.9002 +- 1.28493      14       good
chromium@494056      23.7517 +- 1.38571      14       good
chromium@494061      23.9357 +- 1.95461      14       good
chromium@494062      ---                     ---      build failure
chromium@494063      23.3972 +- 1.62223      14       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.bNp2h.3.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/8970001409284607872


For feedback, file a bug with component Speed>Bisection

ref build moves too.