fix concurrent map panic when querying and committing concurrently #34
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.
benchstat:
Perf tested using
https://github.com/p0mvn/perf-osmo
with the following settings:Meaning, it was concurrently sending 10000 queries over the last 1000 heights chosen randomly through 100 connections. No failure has occurred.
Also tried the following:
Sending 1000 queries over the last 1000 heights through 200 connections.
Result: The deadlock has not occurred and the node handled load well