feat(core): batch heavy write operations #1358
Open
Conversation
This file contains 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
jrchatruc
force-pushed
the
batch-heavy-write-operations
branch
from
c310f7f
to
67590b7
Compare
jrchatruc
force-pushed
the
batch-heavy-write-operations
branch
from
67590b7
to
4dec142
Compare
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.
Motivation
This PR batches the three current heaviest db write operations on the node (
add_block,store_receipts, andcommit_node) so that a single db transaction is used for them. This reduces the time spent flushing to disc withmsync(onlibmdbx) orfsync(onredb) from around ~40-50% to ~0.35%.Non-batched version:
Batched version (the
msyncon this flamegraph is one of the tiny red bars to the left):Description