-
Notifications
You must be signed in to change notification settings - Fork 478
Close short-lived connections first #1509
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
Labels
exp/intermediate
Prior experience is likely helpful
good first issue
Good issue for new contributors
help wanted
Seeking public contribution on this issue
Comments
maschad
added a commit
to maschad/js-libp2p
that referenced
this issue
Dec 13, 2022
maschad
added a commit
to maschad/js-libp2p
that referenced
this issue
Dec 13, 2022
maschad
added a commit
to maschad/js-libp2p
that referenced
this issue
Dec 13, 2022
maschad
added a commit
to maschad/js-libp2p
that referenced
this issue
Dec 16, 2022
maschad
added a commit
to maschad/js-libp2p
that referenced
this issue
Dec 16, 2022
ckousik
pushed a commit
to ckousik/js-libp2p
that referenced
this issue
Jan 24, 2023
…ibp2p#1517) When choosing connections to close, choose shorter lived connections over longer lived ones. Closes libp2p#1509
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
exp/intermediate
Prior experience is likely helpful
good first issue
Good issue for new contributors
help wanted
Seeking public contribution on this issue
When breaching connection limits or the max allowable event loop delay the connection manager can close some connections. It chooses the connections to close by sorting them by the sum of all tags for the remote peers. It should also sort by connection lifespan (e.g. the connection.timeline.open property) to favour long-lived connections.
The text was updated successfully, but these errors were encountered: