Refactor WildcardUtil to improve performance fastMatch #69
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
WildcardUtil.fastMatch was heavily called and generated a ton of garbage, including from mods. Regular wildcards no longer use Regex. Instead, it uses an iterative algorithm with minimal overhead. For cases with @, a cache of compiled regular expressions is used. We've seen a reduction in the method load from 26 seconds to 7. The total allocation reduction by this method is about 25 GB.
A method for clearing this cache has been added. But it's best to clear it after exiting the world. Do you know where to insert this clearing call?
The same modpack is used.