Merged
Conversation
MutinyNet's much longer chain history makes the wallet's mempool handling noticeably more expensive. Recent work moved that work off the async executor to improve the runtime performance but a single poll can still consume nearly the full 2 second interval creating constant CPU pressure. Raise the interval to 10 seconds as a temporary mitigation. It reduces steady background CPU load without changing the underlying behavior, and buys time until the BDK performance issue is fixed.
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
1 participant
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.
MutinyNet's much longer chain history makes the wallet's mempool handling noticeably more expensive. Recent work moved that work off the async executor to improve the runtime performance but a single poll can still consume nearly the full 2 second interval creating constant CPU pressure.
Raise the interval to 10 seconds as a temporary mitigation. It reduces steady background CPU load without changing the underlying behavior, and buys time until the BDK performance issue is fixed.