-
Notifications
You must be signed in to change notification settings - Fork 12
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
Wakurtosis retro #131
base: develop
Are you sure you want to change the base?
Wakurtosis retro #131
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
sembr 🙏 |
Could you please apply sembr to this post @Daimakaimura |
@0xFugue could you please have a look too? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this post :).
My comments are in-line.
The main issue, imo, is confusion around hardware problems seemingly being connected to Kurtosis,
but the only connection is Kurtosis not allowing a multi-machine setup.
You could set-up a red thread through the post by explaining that our simulations need high hardware requirements, and, because of this, Kurtosis only being able to run on a single machine does not allow us to scale simulations. That should also be part of the abstract.
@AlbertoSoutullo could please also check my comments, and check if you have some input 🙏 |
Thanks for the review @kaiserd |
Co-authored-by: kaiserd <[email protected]>
Co-authored-by: kaiserd <[email protected]>
Co-authored-by: kaiserd <[email protected]>
Co-authored-by: kaiserd <[email protected]>
Co-authored-by: kaiserd <[email protected]>
Co-authored-by: kaiserd <[email protected]>
Co-authored-by: kaiserd <[email protected]>
…into wakurtosis-retro
TL;DR
The Wakurtosis framework aimed to simulate and test the behaviour of the Waku protocol at large scales but faced a plethora of challenges that ultimately led us to pivot to a hybrid approach that relies on Shadow and Kubernetes for greater reliability, flexibility, and scaling. Here we will discuss some of the most important issues we faced and their potential solutions in a new hybrid framework.