perf: optimization of map access #692
Merged
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.
Changes
Optimization of map access.
Notes
Probably, more optimizations can be done. This PR covers just author's recent experience.
Details
The way original code (loop only) can look like in terms of Go assembler - refer to https://godbolt.org/z/j8eYrT9jh (x86-64, gc 1.24.2):
The way new code (loop only) can look like in terms of Go assembler - refer to https://godbolt.org/z/r83o1E6as (x86-64, gc 1.24.2):
The new code doesn't have 2 calls of
runtime.mapaccess1_fast64(CALL runtime.mapaccess1_fast64) comparing to old code. I guess, it means that the new code is more optimal.