Optimize map capacity allocation during shard initialization. #419#420
Merged
Merged
Conversation
janisz
approved these changes
Feb 5, 2026
Collaborator
|
One test is failing |
Contributor
Author
I ran the TestCacheReset test locally and didn't encounter any failures. Could you please help me troubleshoot or rerun the test? |
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
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.
If StatsEnabled is configured as false, No need to initialize the capacity for hashmapStats.
This is because the data is not used in subsequent processes, resulting in the allocation of invalid memory space.