-
Notifications
You must be signed in to change notification settings - Fork 6
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
Performance testing of PoA networks #11
Comments
Few more things
Network tests need to be performed for different consensus algorithms, if they are available. Also I think it's important that these tests be performed while network is under constant load of newly established & dropped external connections. As an illustration, on sokol, there are approx. 5-10 new connections to a node per second. Most of them are "spam" (incorrect genesis, incorrect clients like geth, mist, ..), so they are dropped quickly. However, I think they influence stability of connection between real nodes (reason have to use |
Also, we have a helpful tool for deployment of POA Network: https://github.com/poanetwork/poa-test-setup. It might be helpful, for those, who will be making performance testing. POA Network can be deployed with a couple of NPM scripts on a local machine. Basic scenarios of deployment are listed in README. |
The configurations for performance tests:
Load profile:
|
First part would be write efficient script to spam a network with thousands tx per second.
|
Abstract
In searching of a perfect PoA setup, we, as software engineers, would need to benchmark different configurations of AuRa setup. One of the few examples would be to find the maximum number of validators under which the AuRa can still perform well. Another example, is decreasing block times to find the optimal balance between a secure network and a fast network.
Rationale
Cases that we need to perform the tests:
Specification
As a result of such tests, the community would need to look at a detailed report with different configuration tests and benchmarks.
Implementation
Only one Parity node is allowed per cloud instance node.
Tests with heavy loads of DDoS transactions needs to be implemented and executed against this network.
The text was updated successfully, but these errors were encountered: