fix: prevent fetching pool transactions every tick #284
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
Currently we fetch receipt of each transaction that is in pending block on every tick, even if we already saw this transaction before. This is causing lots of requests as block can have ~400 transactions sitting in it for minutes and we hit it every 2 seconds. Now instead of fetching those and skipping this in handlePool we skip those before they are even fetched.
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.
Currently we fetch receipt of each transaction that is in pending block on every tick, even if we already saw this transaction before.
This is causing lots of requests as block can have ~400 transactions sitting in it for minutes and we hit it every 2 seconds.
Now instead of fetching those and skipping this in handlePool we skip those before they are even fetched.