-
Notifications
You must be signed in to change notification settings - Fork 925
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(share/p2p/peer-manager): limit amount of stored pools in peer-manager #3005
feat(share/p2p/peer-manager): limit amount of stored pools in peer-manager #3005
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.
Initial glimpse. Did you run the node to see stable mem usage? I can help with that
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #3005 +/- ##
==========================================
- Coverage 50.94% 50.68% -0.26%
==========================================
Files 176 176
Lines 11190 11172 -18
==========================================
- Hits 5701 5663 -38
- Misses 4986 5012 +26
+ Partials 503 497 -6 ☔ View full report in Codecov by Sentry. |
Yes, memory leak is solved. |
… peer-manager-memory-leak # Conflicts: # share/p2p/peers/manager.go
…nager (celestiaorg#3005) This PR introduces `amountOfStoredPools` param to Peer manager, that will limit amount of stored pools. Defautlt value is 10 pools. Peer manager will try to keep `amountOfStoredPools` amount of pools only for recent headers. Older blocks don't need to be routed by manual pools and could be routed to any full node, as those are expected to have the block by that time. This will lower memory footprint of peer manager as well as resolve memory leaking issues. Resolves celestiaorg#1781
This PR introduces
amountOfStoredPools
param to Peer manager, that will limit amount of stored pools. Defautlt value is 10 pools. Peer manager will try to keepamountOfStoredPools
amount of pools only for recent headers. Older blocks don't need to be routed by manual pools and could be routed to any full node, as those are expected to have the block by that time.This will lower memory footprint of peer manager as well as resolve memory leaking issues.
Resolves #1781