Repository navigation
Performance win: Set up baseline profiles and startup profiles. - #7055
Merged
Merged
Conversation
dbrant
requested review from
Williamrai,
cooltey and
voyagerfan
as code owners
October 23, 2026 12:26
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Modern best practices tell us to include baseline profiles and startup profiles in our app, since the Android ecosystem is so riddled with tech debt that it requires us (the developers) to care about the minutiae of how the app will be JITted on users' devices.
classes.dexfile, so that only the first dex file needs to be loaded upon startup.These profiles should be regenerated once in a while, or whenever we make significant changes to the user journey when the app starts up.
This should be independent of obfuscation.