Avoid String concatenation for lookup in StaticMessageSource#22451
Closed
stsypanov wants to merge 1 commit into
Closed
Avoid String concatenation for lookup in StaticMessageSource#22451stsypanov wants to merge 1 commit into
stsypanov wants to merge 1 commit into
Conversation
68eb1d6 to
3a3058b
Compare
Contributor
Author
|
@jhoeller I've slightly simplified the patch to use Array.asList |
3a3058b to
e4241fd
Compare
Contributor
Author
|
@jhoeller hello, any updates on this? |
Contributor
|
On review, I'll rather go with a nested As a side note, part of the original design of I'll repurpose this issue accordingly. Thanks for the PR, in any case! |
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.
Currently StaticMessageSource employs String composed of key and stringified Locale as key in map:
As a result at each call to
Map::get/Map::putwe have to concat Strings resulting in allocations ofStringBuilderand copyingchar[]. Instead I propose to use separately defined immutable Key.I've tested behaviour with benchmark
Patched consumes much less memory on key allocation and does it faster, performance of equals/hashCode is mostly the same (tested at work on i7-7700):