New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transaction Pool flooding and possible solutions (e.g. Throttling) #1313

Closed
faustbrian opened this Issue Nov 7, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@faustbrian
Collaborator

faustbrian commented Nov 7, 2018

The issue with the transaction posting endpoints getting slower over time is related to general performance of the node. It basically boils down to performance degradation of a node if it gets spammed which is caused by more CPU getting used which in turn results in the crypto operations like verification of transactions slowing down of which the end-result is a long response time.

For now we changed the default config to allow less transactions per request (2349439) which helps the issue but is just a bandaid. Another solution is throttling, even on the P2P layer, which can be touchy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment