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

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


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

android-nexus5X

===== 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@385649         37678.375   1044.469645 8           good
chromium@385694         37554.666667641.816381  6           bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 602323

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests page_cycler.intl_ko_th_vi
Test Metric: vm_private_dirty_final_browser/vm_private_dirty_final_browser
Relative Change: 1.44%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/71
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9015660710924307552


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

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

re-kicked bisect with modified range.

re-kicked again (though the 5X bots may be offline so I'm not sure results will come in)

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


===== SUSPECTED CL(s) =====
Subject : Add a new performance benchmark test for postMessage
Author  : peria
Commit description:
  
BUG= 148757 
TEST=tools/perf/run_benchmark run blink_perf.bindings

Review URL: https://codereview.chromium.org/1871463002

Cr-Commit-Position: refs/heads/master@{#385719}
Commit  : f4ff9e2d8d11f1c4d2225c37dddc4c755dbd2c32
Date    : Thu Apr 07 12:16:06 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@385658         153.172481  4.720318    5           good
chromium@385704         144.792275  2.526721    5           good
chromium@385716         143.427835  3.32854     5           good
chromium@385718         151.970744  7.056536    5           good
chromium@385719         125.72471   8.466576    5           bad         <-
chromium@385722         111.345697  12.984957   5           bad
chromium@385727         122.500135  21.781963   5           bad
chromium@385750         102.129531  20.011779   5           bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 602323

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.bindings
Test Metric: set-attribute-rare/set-attribute-rare
Relative Change: 33.32%
Score: 99.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/120
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9014308717187889488


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

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