summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator.cpp
diff options
context:
space:
mode:
authorJorim Jaggi <jjaggi@google.com>2018-07-09 17:57:10 +0200
committerJorim Jaggi <jjaggi@google.com>2018-07-13 13:20:48 +0000
commit7119800f4b4c78b5e40df205a391c400c10d2f01 (patch)
treeb4f04c7d04ace6434c85bf3e3e3c393eb4283cb2 /tools/aapt2/java/JavaClassGenerator.cpp
parent5c75b5b60e7ec757884d71ae2dd12ee1c71614a1 (diff)
Pin compiled code of HOME app
Keeping the code in memory of the currently set home app is important for latency as we don't have any kind of starting window/splash screen when pressing the home app to hide any latency. Memory impact: Pinning dex/vdex: In practical scenarios, this should be < 500kb. The home app is usually profile-speed compiled, for which the resulting dex/vdex files are about 2 mb. However, during regular use, at least 1.5 MB of it is referenced in memory. This makes sense: By definition profile-speed only compiles the things that is usually frequently executed during regular execution. Pinning apk: With Launcher 3 in practical scenarios this should be about 3.7 MB, as the APK is about 5.7 MB but 2 MB are usually referenced in any case. Bug: 111132016 Bug: 78585335 Test: Inspect "adb shell dumpsys pinner" after boot. Test: Check for pinned files after updating camera/home. Test: Check for pinned files after user switch with different default apps. Test: Check for pinned files after bg-dexopt. Test: Check for pinned files after bg-dexopt + kill pid. Change-Id: I6cdbc06d089efeb1c72a51216879ba0573502009 Merged-In: I6cdbc06d089efeb1c72a51216879ba0573502009
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions