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

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


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

android-nexus6

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

=== Auto-CCing suspected CL author huapengl@amazon.com ===

Hi huapengl@amazon.com, 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 : Use "-Os" for Android or IOS in "optimize_max" config
Author  : huapengl
Commit description:
  
Using "-Os" would benefit both Android and IOS build, because "-Os" does
"-O2" optimizations and code size improvement.

libchrome.so drops from 44MB to 42 MB.
ChromePublic.apk drops from 47 MB to 45 MB.

BUG=621335

Review-Url: https://codereview.chromium.org/2158053002
Cr-Commit-Position: refs/heads/master@{#406304}
Commit  : 2bb3c4f7a7c7632afe1b63a19d49daa61bbfc37b
Date    : Tue Jul 19 17:21:48 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@406284  30414.0  266.725  5  good
chromium@406295  30289.2  114.994  5  good
chromium@406301  30259.5  108.091  5  good
chromium@406303  30374.5  105.873  5  good
chromium@406304  32862.5  167.179  5  bad    <--
chromium@406306  32833.9  116.793  5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 629798

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: Total/Total
Relative Change: 7.96%
Score: 99.9

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


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

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

It looks like we should revert the CL.

revert:
https://codereview.chromium.org/2164973002/

Thanks for the revert. There was quite a bit of regressions due to this. If you are planning to land this (or something similar) please again give a heads up to perf-sheriffs@.

somehow the de-duplication did not leave a comment here but here are the other duplicates issues: issue 629809, issue 629810

Reverting recovered the regression.

FYI this also regressed sizes. Just triaged the alerts to this bug if you want to take a look.