Do DB insertions in parallel #71
Merged
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
When inserting new gossip into the DB, we block the LDK peer handling if we get behind. This is mostly okay, but can cause ping timeouts and reconnections, which isn't ideal. To limit how often we should see this, here we move to doing the new gossip insertions in parallel.
arik-so
approved these changes
Jan 29, 2024
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.
When inserting new gossip into the DB, we block the LDK peer handling if we get behind. This is mostly okay, but can cause ping timeouts and reconnections, which isn't ideal. To limit how often we should see this, here we move to doing the new gossip insertions in parallel.