perf: Replace BucketIterator with function#258
Merged
frankdavid merged 4 commits intomainfrom Dec 4, 2024
Merged
Conversation
|
dsarlis
previously approved these changes
Dec 4, 2024
dsarlis
approved these changes
Dec 4, 2024
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.
Iterating through the buckets with
BucketIteratorwas nice because we could use a for loop but the compiler cannot optimize it as well as a function that takes a callback. Since this code has to be run on every single memory read/write, making it as efficient as possible is crucial. Using a function not only allows for better wasm generation but we can further optimize the implementation more easily (e.g. we can add a TLB-like cache).