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
{{ message }}
This repository has been archived by the owner on Sep 9, 2022. It is now read-only.
We also need a mechanism to tag connections used as relay reservations, so that we don't drop them off the relay unnecessarily.
I think we need a RESERVE message, which should tag the connection in the cm.
So given our observations regarding relay traffic and the discussion in #67 I think we want to do the opposite when operating as a relay. We should tag connections according to their hop count, so that when the connection manager decides to prune, we prune the idle connections first.
We might also want to have an option to explicitly enable that, as it could wreak havoc with the tagging from other subsystems.
We should integrate with the connection manager to deprioritize relay-hop connections when under heavy load.
The text was updated successfully, but these errors were encountered: