Replies: 2 comments
-
interesting! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm looking at the performance of Android builds, particularly for large apps that are being developed on cloud developer instances. I though that incremental installs via
bazel mobile-install
would be killer in this environment, but we're not seeing improvements at all. We created a simple app with a single very large resource (foo.bin) to test this out and look at timing.Reading between the lines in incremental_install.py lines 775 - 784, it looks like the steps are basically:
Tweaking things and running them generates expected output (updating code indicates that a dex is being copied, but resources are not, updating resources indicates that resources are being copied but a dex is not). But that last step is where we're hitting a snag. The _incremental.apk contains all of the resources. Looking at the contents of that file I see:
So clearly my foo.bin is bloating the size of this incremental apk.
Is this intentional? Is there a way to ensure that this apk has only the bare minimum resources necessary so that we don't have to transfer this on every install?
Beta Was this translation helpful? Give feedback.
All reactions