New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Concurrent cache of generated classes #53
Merged
Merged
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
Previously KeyFactory generated java.lang.Class fields even with CLASS_BY_NAME customization. That might lead to unexpected class and classloader leak. The fix ensures KeyFactory uses java.lang.String to store class names. It should make no harm as CGLIB uses per-classloader cache, thus class name should be sufficiently unique
… calculation performance
vlsi
force-pushed
the
concurrent_cache
branch
from
November 16, 2015 15:52
729dcd6
to
615f3b6
Compare
Please, review the PR & approach. In a couple of words:
|
vlsi
force-pushed
the
concurrent_cache
branch
from
November 16, 2015 17:39
615f3b6
to
05f830f
Compare
Anybody there? |
raphw
pushed a commit
that referenced
this pull request
Feb 5, 2016
Concurrent cache of generated classes
The cache is definetly a pain-point in cglib. This is a real improvement! Request looks good! |
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 fix removes
synchronization
in case relevant class is already cached.The change comes on top of "fix permgen" (it reuses
WeakIdentityKey
)Measurements (java 1.8u60, i7-4960HQ CPU @ 2.60GHz):
#1 Thread
Response time is 15 times better.
Heap allocation is 5 times less.
Before:
After:
Multiple threads
Good scalability in range of 1-2-4 threads.
Degradation after 4 is somewhat expected as the machine has just 4 hw cores.
Before:
After: