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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx4zJiwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx6u6sQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp7rCrwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx_r54AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx7LupAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp-6bvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx4zJiwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx_ii5goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx_axlQoM


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

android-nexus5X
android-nexus6

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev   N   Good?
chromium@435243  32900398  14212120  27  good
chromium@435263  33298848  12518091  27  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 670692

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.facebook v8.browsing_mobile_ignition
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_avg/browse_social/browse_social_facebook
Relative Change: None

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


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

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

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

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

This does not look like a real regression. There was an improvement in the range 432219-432873 and after few revisions it has gone back to the same state again. I could not find any strong suspect that could have caused either the improvements or regressions. Though I am not totally sure. 

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@435243  30280257  7161713  26  good
chromium@435263  30919692  7507294  27  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 670692

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.washingtonpost v8.browsing_mobile_ignition
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_max/browse_news/browse_news_washingtonpost
Relative Change: 2.11%

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


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

| 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 JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev   N   Good?
chromium@435243  58570748  17529760  27  good
chromium@435263  58026956  24008523  27  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 670692

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.youtube v8.browsing_mobile_ignition
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_max/browse_media/browse_media_youtube
Relative Change: 0.93%

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


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

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

This is because of a change in configuration on the from arm64 to arm32. The configurations are switched back to arm64 (https://github.com/catapult-project/catapult/issues/3050#issuecomment-263893540). The graphs have also recovered. Marking it as won't fix.

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

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