Optimize primitive boxing #2
Open
Conversation
This file contains 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
added 5 commits
October 10, 2016 16:14
In order to avoid the creation of multiple Integer instances, use Integer#valueOf instead of Integer#new. This reduces memory and gc load.
In order to avoid the creation of multiple instances of true/false, use Boolean#valueOf instead of Boolean#new. This reduces memory and gc load.
These changes remove some superfluous boxing/unboxing operations and prepare for future JVM optimization similar to the Integer cache.
These changes help to exploit the Long cache.
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.
This pull request reduces memory strain and improves performance by avoiding the creation of duplicated primitive wrapper objects. To achieve this it exploits a) Java's built-in caches, e.g., IntegerCache (configure: -XX:AutoBoxCacheMax=) and b) auto-boxing.