-
Notifications
You must be signed in to change notification settings - Fork 314
Make RawTable::insert_no_grow
unsafe
#254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this function is already unsafe, we could add an extra
assume_no_deleted
argument which assumes that the table is fresh and does not contain anyDELETED
entries? This would skip the check onold_ctrl
and might improve performance in some cases.However it might be exposing too much of the hash table internals. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So
assume_no_deleted
would still be a condition there, but one that you would hope is constant-propagated?I think it's too much of a micro-optimization, especially for exposing internals. I ran some
indexmap
benchmarks that are heavy onrebuild_hash_table
, which is aclear
followed by a loop ofinsert_no_grow
. About 50% of that function's perf profile is simply thebucket.write
, mostly due to cache misses. Most of the remaining time is spread around finding the insert slot, and less than 4% on updatinggrowth_left
. I even tried hard-coding that togrowth_left -= 1
, but the difference was lost in the noise.