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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgmv_eqQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgmqfBtgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2piXqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg6v3C4wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgmqewqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgmt2uuAsM


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

android-galaxy-s5
android-nexus5
android-nexus6
android-nexus7v2
android-one

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

Judging from the range this is likely cef5cfa8e1e017d0818979d820ea77023d50fd11. amistry, can you take a look?

Yes, it almost certainly is. But the perf dashboard is difficult to use and I can't tell whether it might be a case of moving CPU usage from another thread onto the IO thread. I don't have time to investigate. Adding fellow Mojo folks.

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Use ChannelMojo for GpuChannels.
Author  : amistry
Commit description:
  
BUG= 604282 
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2127693002
Cr-Commit-Position: refs/heads/master@{#406719}
Commit  : cef5cfa8e1e017d0818979d820ea77023d50fd11
Date    : Thu Jul 21 00:13:59 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev     N  Good?
chromium@406714  2.66292  0.0329891   5  good
chromium@406717  2.65929  0.0285675   5  good
chromium@406718  2.64352  0.00971341  5  good
chromium@406719  3.24202  0.0481241   5  bad    <--
chromium@406720  3.36142  0.00982134  5  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 630453

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests thread_times.key_silk_cases
Test Metric: thread_IO_cpu_time_per_frame/thread_IO_cpu_time_per_frame
Relative Change: 26.23%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3856
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006485683908253968


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5777235861045248

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!