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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxpSKrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICguv_svwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghqCOqwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICguqjTxQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghuSGswoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghuTIvQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghpzc-QoM


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

android-nexus6

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

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

Hi ianwen@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : [Android] Roll support lib to 24.1.1
Author  : ianwen
Commit description:
  
This is the second attempt to roll the support library. The first
attempt was https://codereview.chromium.org/2175513002 and it was
reverted in https://codereview.chromium.org/2175763003 due to downstream
bots failure.

BUG=629768

Review-Url: https://codereview.chromium.org/2185133002
Cr-Commit-Position: refs/heads/master@{#408211}
Commit  : c8ba82433d4b45be103fc3f3b0005d6df5c82a64
Date    : Wed Jul 27 19:18:31 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@408186  26079.3  41.7117  6  good
chromium@408201  26071.4  32.7154  5  good
chromium@408209  26044.4  60.0566  5  good
chromium@408210  26046.0  45.5686  5  good
chromium@408211  26403.6  40.5869  5  bad    <--
chromium@408213  26384.2  29.5669  5  bad
chromium@408216  26397.2  43.8771  5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 632644

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler.basic_oopif
Test Metric: vm_private_dirty_final_browser/vm_private_dirty_final_browser
Relative Change: 1.23%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2374
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005812761845528112


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

| 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 checking in: any update on this regression Ian? It seems to be a reasonably significant regression in memory usage from the support library roll. Is there anything we can do to mitigate this?

I don't know how to improve this. The regression is indeed strongly associated with us updating the support lib. Yet I do not know how to address this.

Adding Maria and Ted, who might give me some suggestions?

Ian, do you have access to the set of changes in the support lib release? It would be helpful if you could find the change responsible for the regression. Then perhaps we can work with Android to fix it?

Perf sheriff ping: reminder to follow up on possible performance issues

Perf sheriff ping

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2678
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

ianwen, did you get a chance to look into this (per #6)?

+cmumford as FYI.

This is hard as we jumped too far ahead from 23.2.1 to 24.1.1, which was three month worth of development, and the support library branches are not even the same.

I will ask the android team about whether we could get a list of commits.

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

Doesn't look like there's a way to address this.