refactor: Switch stake address state from Mutex<HashMap> to DashMap #113
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.
The
stake_addresses
field inaccounts_state
was previously using aMutex<HashMap>
to store stake address state. As the newStateQuery
message type is adopted, read access tostake_addresses
is becoming increasingly frequent, a trend that will continue as additional cross-module queries are implemented.This PR refactors
stake_addresses
to useDashMap
instead ofMutex<HashMap>
, enabling fine-grained locking for writes and allowing fully concurrent reads. This significantly reduces contention under load, such as when syncing to tip.I had observed that some
StateQuery
messages fromdrep_state
toaccounts_state
were timing out. After switching toDashMap
, these timeouts were resolved.