Fixed the aggressive eviction of txns in txn pool #1149
Merged
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.
Description
This is a cherry pick merge of this geth upstream PR: ethereum/go-ethereum#21300
During load tests, we saw that txns were being very aggressively evicted from the txpool (in some cases evicted within a second of being added to it). This caused the submitted txn to never be propagated throughout the network. Also, based on how our load tests are designed, this bug was preventing us to saturate the block chain.
After making this change, our load tests are able to saturate the block chain.
Testing
As part of the original upstream PR, there are unit tests that verify that txns are not evicted early. Also, our load tests is able to confirm that the txns are not evicted early (and hence can saturate the chain).
Backwards compatibility
Is backwards compatible