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

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


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

android-nexus9

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@385709         1404.691667 17.342615   12          good
chromium@385738         1406.9      8.373939    8           bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 602322

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests blink_perf.pywebsocket
Test Metric: fetch-receive-blob-worker-async-verify/fetch-receive-blob-worker-async-verify
Relative Change: 0.90%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1730
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9015660720590488032


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

| 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!

 Issue 603254  has been merged into this issue.

Merging report for android-nexus7v2.

 Issue 602321  has been merged into this issue.

The increase is slight. I've changed this to P3 for now.

https://chromeperf.appspot.com/group_report?bug_id=603254
https://chromeperf.appspot.com/group_report?bug_id=602322
https://chromeperf.appspot.com/report?sid=40c2104ba4e6055904cfb0d01a7585585b2d4c517b495aae02e0b12a4f833ef0&rev=385709

Trying some more bisects.

Kicked off another bisect: https://chromeperf.appspot.com/buildbucket_job_status/9013373171070949312

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@385700  1407.59  13.7807  12  good
chromium@385738  1391.46  15.3965  8   bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 602322

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.pywebsocket
Test Metric: fetch-receive-blob-worker-async-verify/fetch-receive-blob-worker-async-verify
Relative Change: 0.33%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1780
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013373171070949312


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

| 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!

Bisect gave up with 8 and 12 samples
Re-kicked another bisect: https://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1790

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@385709  1417.33  17.8724  12  good
chromium@385738  1419.4   8.81103  8   bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 602322

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.pywebsocket
Test Metric: fetch-receive-blob-worker-async-verify/fetch-receive-blob-worker-async-verify
Relative Change: 0.35%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1790
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9012831968042227136


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

| 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!

Perf sheriff ping

Blocked on  issue 598215 , no need to triage this until that issue is resolved, I believe.

Only failed on N9s. WontFix.