You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a great tool, what I have and a few other teams I have been talking to are looking for. For next version Id love to suggest some possible improvements/extra features
More examples and documentation, I have started to set up this repo, and can hopefully add more generalized tests and it can be used as examples for other teams
A before each hook that resets the state of the dev chain (I know this is hard and will probably require an RPC call on the substrate side, but worthwhile to look into)
Access to more features of Polkadot JS. When trying to call random RPC calls like account next nonce and signing with a different nonce (to bombard the node with tx) see here I had to manually pull in the polkadot js api.
An option to store results in a postgres DB for later use (optional, maybe not the best idea, but worth thinking about)
Documentation to set this up with Grafana
A call that load tests a chain and can give some sort of printout to an approx tps and if it is good or bad. As well to set failures on min tps for a specific call so it can be run in a pipeline
The text was updated successfully, but these errors were encountered:
Yes, it's a very useful feature, but - as you rightly note - this is hard for development. But we thinking about it and have some ideas
I need some times to research this question, maybe it's will be done soon
It is my opinion that the responsibility is not for this tool, you can do it manually. Some people don't need to save results to a DB or may want to use a different DB instead of Postgres.
This is a great tool, what I have and a few other teams I have been talking to are looking for. For next version Id love to suggest some possible improvements/extra features
More examples and documentation, I have started to set up this repo, and can hopefully add more generalized tests and it can be used as examples for other teams
A before each hook that resets the state of the dev chain (I know this is hard and will probably require an RPC call on the substrate side, but worthwhile to look into)
Access to more features of Polkadot JS. When trying to call random RPC calls like account next nonce and signing with a different nonce (to bombard the node with tx) see here I had to manually pull in the polkadot js api.
An option to store results in a postgres DB for later use (optional, maybe not the best idea, but worth thinking about)
Documentation to set this up with Grafana
A call that load tests a chain and can give some sort of printout to an approx tps and if it is good or bad. As well to set failures on min tps for a specific call so it can be run in a pipeline
The text was updated successfully, but these errors were encountered: