-
Notifications
You must be signed in to change notification settings - Fork 447
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
refactor: Remove parallel dialling #2090
Labels
kind/architecture
Core architecture of project
P1
High: Likely tackled by core team if no one steps up
topic/perf
Performance
Comments
maschad
added
kind/architecture
Core architecture of project
need/triage
Needs initial labeling and prioritization
topic/perf
Performance
P1
High: Likely tackled by core team if no one steps up
and removed
need/triage
Needs initial labeling and prioritization
labels
Sep 28, 2023
maschad
changed the title
Refactor: Remove parallel dialling
refactor: Remove parallel dialling
Oct 2, 2023
maschad
added a commit
to maschad/js-libp2p
that referenced
this issue
Oct 18, 2023
3 tasks
3 tasks
achingbrain
pushed a commit
to maschad/js-libp2p
that referenced
this issue
Oct 31, 2023
Since we are now dialling one peer at a time as a means of smarter dialling, we no longer need the option to control the concurrency of parallel dials across a single peers' multiaddrs. Closes libp2p#2090
achingbrain
added a commit
that referenced
this issue
Oct 31, 2023
Since we are now dialling one peer at a time as a means of smarter dialling, we no longer need the option to control the concurrency of parallel dials across the multiaddrs of a single peer. Closes #2090 --------- Co-authored-by: Alex Potsides <[email protected]>
achingbrain
pushed a commit
that referenced
this issue
Nov 21, 2023
Since we are now dialling one peer at a time as a means of smarter dialling, we no longer need the option to control the concurrency of parallel dials across a single peers' multiaddrs. Closes #2090
3 tasks
achingbrain
pushed a commit
that referenced
this issue
Nov 21, 2023
Since we are now dialling one peer at a time as a means of smarter dialling, we no longer need the option to control the concurrency of parallel dials across a single peers' multiaddrs. Closes #2090
achingbrain
added a commit
that referenced
this issue
Nov 21, 2023
Since we are now dialling one peer at a time as a means of smarter dialling, we no longer need the option to control the concurrency of parallel dials across a single peers' multiaddrs. Closes #2090 Co-authored-by: chad <[email protected]>
Merged
maschad
added a commit
to maschad/js-libp2p
that referenced
this issue
Nov 27, 2023
Since we are now dialling one peer at a time as a means of smarter dialling, we no longer need the option to control the concurrency of parallel dials across a single peers' multiaddrs. Closes libp2p#2090 Co-authored-by: chad <[email protected]>
Closed
This was referenced Jan 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/architecture
Core architecture of project
P1
High: Likely tackled by core team if no one steps up
topic/perf
Performance
As it stands we currently have parallel dials per peer disabled by default, post #2010 there is currently no use case for parallel dials per peer given that if we have ranked multiaddrs based on likelihood of success, it would be inefficient to dial multiaddrs that could potentially fail.
The text was updated successfully, but these errors were encountered: