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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-JXCrwoM


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

android-nexus5X

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

=== Auto-CCing suspected CL author mtklein@chromium.org ===

Hi mtklein@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Mike Klein
  Commit : 86125483f93fb9be7c90e1cea03054a1e0e80449
  Date   : Fri Feb 17 17:46:43 2017
  Subject: Revert "Revert "Take missed opportunity: memset for A8.""

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : webrtc.peerconnection
  Metric       : cpu_utilization/cpu_utilization_browser
  Change       : 17.01% | 19.0761077391 -> 15.831898998

Revision                             Result                   N
chromium@451419                      19.0761 +- 0.779487      6      good
chromium@451433                      18.85 +- 1.09514         6      good
chromium@451440                      18.8504 +- 1.11638       6      good
chromium@451442                      18.969 +- 1.01901        6      good
chromium@451443                      19.0191 +- 1.0039        6      good
chromium@451443,skia@d8ebf69f0a      18.8689 +- 0.803012      6      good
chromium@451443,skia@02241e976b      18.7807 +- 0.950225      6      good
chromium@451443,skia@86125483f9      15.9044 +- 0.943349      6      bad       <--
chromium@451443,skia@7d07d46638      15.6442 +- 0.516856      6      bad
chromium@451443,skia@561d1f8153      15.6576 +- 0.494376      6      bad
chromium@451444                      15.9187 +- 1.19595       6      bad
chromium@451447                      15.8319 +- 0.72666       6      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 webrtc.peerconnection

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8985132737431321648

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6178650002554880


| 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 Speed>Bisection.  Thank you!

Is this just FYI, or am I supposed to do something here?  Isn't a 12.7% improvement good?

Just FYI, in case it was unexpected.