-
Notifications
You must be signed in to change notification settings - Fork 56
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
Hyperledger Besu / Pantheon testing #11
Comments
Good idea. Are you experienced in that? |
Not yet, unfortunately. |
We are building a tool for this based of the chainhammer fork and will open source when done. |
WOW. Cool. Much appreciated, @Genysys . By now you have probably noticed that chainhammer is not more (but also not less) than a collection of very simple scripts. I got it all working well though (and also eventually very much automated, via ugly bash scripts); and it has helped already to find parity configurations, measure the Azure BaaS product, etc.. I think most of the code is well documented. The bash stuff not so much, though. Any questions just ask. Thanks! |
I forked chainhammer to work with Pantheon/Besu (with I'm learning Go lang so, I think I will do another fork, in order to practise.. :D |
Thanks a million. When I've come full circle, and will be back and updating all on Ethereum-type benchmarking to all the newest versions, I would like to add 'Hyperledger Besu / Pantheon' to the list of to be benchmarked platforms. You could help, by providing such scripts:
As examples for what I expect there, see https://github.com/drandreaskrueger/chainhammer/tree/master/networks Moreover, please provide an orchestration, with 3-4 hyperledgerbesu nodes running on the same machine, ideally all dockerized. Thanks a lot! |
Any plans to include and test the Hyperleder Besu/Pantheon client with Clique and/or IBFT?
Very curious to see how that compares vs. the others.
The text was updated successfully, but these errors were encountered: