GitLab

After collecting data on Android canary/dev, we are going to fold this
project into "reducing compositing under memory pressure" so we only
stop compositing trivial 3D transforms when under memory pressure. This
achieves the majority of the OOM benefits with minimal user impact. This
experiment resulted in interesting data about the effects of memory
savings on OOM crash rates. On canary/dev Android, the experiment showed
a decrease in GPU tile memory (-2.4% @ 50th, -4.4% @ 99th) resulted in a
decrease in peak GPU memory usage (-1.95% during scroll), a decrease in
memory pressure signals (-6% critical), and a decrease in crashes
(-8.25% visible renderer foreground OOM). These benefits came at a cost
of additional raster which could be seen in
Scheduling.Renderer.DrawIntervalWithMainThreadAnimations2 which
increased 4.66% at the 99th. More information can be found in:
https://docs.google.com/document/d/1yFSWUhHjneEnjx_vf9SBpYAQOoce8JMbtTvAiHhGD-o

Bug: 1012775
Change-Id: I9ce1c4f47860d9ab0dbd7cbae68662cf4d657885
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1981804
Auto-Submit: Philip Rogers <pdr@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#727972}