Skip to content
This repository has been archived by the owner on Sep 26, 2019. It is now read-only.

Discard known remote transactions prior to validation #1548

Merged

Conversation

ajsutton
Copy link
Contributor

PR description

On MainNet we receive a lot of incoming remote transactions (up to 1,000 messages/sec which may contain multiple transactions). Currently, we validate each transaction, then check if it's already in the transaction pool. Instead, we should check if the transaction already exists and immediately discard it if so.

It's still possible that we'll wind up validating the same transaction twice (at the same time) because it wasn't present, two threads started validation and ultimately only one will actually be able to add it. However, since we only have two threads handling incoming transaction messages, the number of times we validate the transaction will be at most twice.

Copy link
Contributor

@usmansaleem usmansaleem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@ajsutton ajsutton merged commit 472a49a into PegaSysEng:master Jun 11, 2019
@ajsutton ajsutton deleted the skip-validation-for-existing-transactions branch June 11, 2019 09:58
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants