Avoid memory waste caused by multiple threads using many FastThreadLocal(#8271 #9328) #1
Conversation
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
…cal (netty#8271 netty#9328) Motivation: Every time one FastThreadLocal is created, the InternalThreadLocalMap.nextIndex is increased. When multiple threads create many FastThreadLocal, the nextIndex will grow big soon. FastThreadLocal is created much later, the InternalThreadLocalMap.indexedVariables is expanded more frequently. But it is unnecessary. Modifications: Change InternalThreadLocalMap.nextIndex to instance variable. FastThreadLocal.index is assigned by InternalThreadLocalMap of current thread. FastThreadLocal.variablesToRemoveIndex is always zero. Result: InternalThreadLocalMap.indexedVariables do not need be expanded when one thread create less than 31 objects of FastThreadLocal.
itkfyeah
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Avoid memory waste caused by multiple threads using many FastThreadLocal (netty#8271 netty#9328)
Motivation:
Every time one FastThreadLocal is created, the InternalThreadLocalMap.nextIndex is increased.
When multiple threads create many FastThreadLocal, the nextIndex will grow big soon.
FastThreadLocal is created much later, the InternalThreadLocalMap.indexedVariables is expanded more frequently.
But it is unnecessary.
Modifications:
Change InternalThreadLocalMap.nextIndex to instance variable.
FastThreadLocal.index is assigned by InternalThreadLocalMap of current thread.
FastThreadLocal.variablesToRemoveIndex is always zero.
Result:
InternalThreadLocalMap.indexedVariables do not need be expanded when one thread create less than 31 objects of FastThreadLocal.