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
Currently, the transport manager never removes the state of disconnected peers.
This leads to increasing memory consumption over time, especially considering that each peer state supports up to 64 addresses.
We would still need to keep disconnected peers around for a sensible amount of time because the peer state provides us with the addresses to dial peers.
One possible solution that takes into account preserving addresses:
extend PeerState::Disconnected with a timestamp; whenever the peer disconnects we keep track of time
periodically (tbd N minutes 1h) remove disconnected peers who are disconnected for more than N minutes
Total number of tracked addresses
Total number of tracked peers
cc @paritytech/networking
The text was updated successfully, but these errors were encountered:
Currently, the transport manager never removes the state of disconnected peers.
This leads to increasing memory consumption over time, especially considering that each peer state supports up to 64 addresses.
We would still need to keep disconnected peers around for a sensible amount of time because the peer state provides us with the addresses to dial peers.
One possible solution that takes into account preserving addresses:
PeerState::Disconnected
with a timestamp; whenever the peer disconnects we keep track of timeTotal number of tracked addresses
Total number of tracked peers
cc @paritytech/networking
The text was updated successfully, but these errors were encountered: