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

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


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

android-one

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

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

Hi junov@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Justin Novosad
  Commit : 5827cd0085ff673f5d89192761a4112e07dbb20c
  Date   : Fri May 26 21:11:30 2017
  Subject: Disable 2D canvas deferred rendering on low end devices

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/load_tools/load_tools_drive
  Change       : 62.17% | 5023864.47619 -> 8147205.42857

Revision             Result                   N
chromium@475066      5023864 +- 20411454      21      good
chromium@475098      2819128 +- 908093        6       good
chromium@475114      4637545 +- 17689022      14      good
chromium@475121      5790070 +- 22896583      14      good
chromium@475125      3299725 +- 3066450       6       good
chromium@475126      3357069 +- 3562004       9       good
chromium@475127      6044675 +- 3497437       9       bad       <--
chromium@475130      6312124 +- 11484255      14      bad
chromium@475194      8147205 +- 22379980      14      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.drive system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8977451122187535824

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5897094465847296


| 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 Speed>Bisection.  Thank you!

Explictly assigning. A CL you landed tripped one of the speed metrics we measure in the lab. If this is the first time this has happened to one of your CLs, or if it's been a while, please read: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/addressing_performance_regressions.md

We're looking for one of the following:
1. Justification via explanation
2. Plan to revert or fix
3. Angry rage throwing of equipment at my head

Just be aware that I'm trained in trumpet playing and First Aid and am not afraid to use it.

Note: This was a bulk edit message and not very personal.

this came back down.