-
-
Notifications
You must be signed in to change notification settings - Fork 306
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
feat: libp2p-gossipsub v10.1.1 #6156
Conversation
Performance Report✔️ no performance regression detected Full benchmark results
|
Do you think we'll get results of your hypothesis by Friday @tuyennhv ? This would be great if it fixes the leak ... and if it requires delaying v1.12.1 until early next week, we can consider that too. |
@philknows yes I think we'll get confirmation by Friday |
We may have to push v1.12.1 to early next week, so you can continue capturing data over the weekend to confirm your thesis. |
posting metrics in the last 3 days since Dec 05
I'd merge this PR through as there is no down side with it https://github.com/ChainSafe/js-libp2p-gossipsub/releases/tag/v10.1.1 @wemeetagain can confirm |
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
update the 64 validator node metrics, it does not seem to be a leak cc @philknows |
🎉 This PR is included in v1.12.1 🎉 |
🎉 This PR is included in v1.13.0 🎉 |
Motivation
There is a memory leak in gossipsub which is potentially fixed in v10.1.1, see ChainSafe/js-libp2p-gossipsub#477 (comment)
Description
Update
libp2p-gossipsub
to v10.1.1 cc @wemeetagainpart of #6129
TODOs
Records the result of different nodes in 1 week