perf(database): use fixed hashmaps in cache db#3231
Merged
Conversation
aaae91e to
ced2552
Compare
ced2552 to
f8578bb
Compare
CodSpeed Performance ReportMerging #3231 will not alter performanceComparing Summary
|
DaniPopes
approved these changes
Dec 17, 2025
Collaborator
DaniPopes
left a comment
There was a problem hiding this comment.
lgtm, new deps are all optional
Member
|
Would be good to explore if we can use these more. @DaniPopes, how do they specialise, use a different hasher? |
Merged
Rjected
pushed a commit
to Rjected/revm
that referenced
this pull request
Dec 19, 2025
* perf(database): cache db fixed hash maps * bump alloy deps
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.
Alloy provides specialized hashmap types for fixed byte keys, such as
AddressandB256. We should use them forCacheDB.