...
| Page properties | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
|
...
I will be regularly performing TPS benchmarks on a set of four machinesbenchmark stand, created by DevOps. This will allow the iroha2 core team consistent insight into how code changes are affecting performance. I will establish a baseline TPS for the LTS release. That way we can make sure all our codebase simplications are improvements and not regressions. Some of this work can be handled by devops once the routine has been established.
...
There are many more things such as these yet to be discovered. I am confident we can reach 50xachieve shockingly good results compared to today. The question is simply how quickly we will get there. Either way performance testing and profiling is essential.
Decisions
Sam H. Smithwill do performance testing on a 4 node benchmarking stand.
Alternatives
We could try set up automated performance testing. - currently quite difficult
Have devops do some of this work.
Simply put, we need to start profiling. Otherwise we won't be able to improve performance.
Anton is working on scripts for us to deploy iroha2 on kubernetes. This is tracked by issue, https://app.zenhub.com/workspaces/iroha-v2-60ddb820813b9100181fc060/issues/hyperledger/iroha/2450.
Once this is done I can gather performance data regularly as mentioned above.
Alternatives
Concerns
There is a concern that time spent optimizing will not be fruitful. Or that the feature requirements will change so that the optimization work is made redundant.
...
We have assumed iroha2 is at least 50-100x slower than it needs to beonly using 1-2 % of the machine's performance.
Risks
Additional Information
...