fix: when creating dial targets, encapsulate PeerIds last#1389
Merged
fix: when creating dial targets, encapsulate PeerIds last#1389
Conversation
It turns out because `Multiaddr.encapsulate` stringifies the `Multiaddr` it's a [suprisingly expensive operation](multiformats/js-multiaddr#275 (comment)) so here we switch the order of our `Multiaddr` pipeline around so we filter undialable addresses (e.g. unsupported transports etc) before encapsulating the `PeerId` onto a `Multiaddr` we'd then just ignore.
Member
Author
|
CPU usage before (left hand side) and after (right hand side) running locally with this change:
|
mpetrunic
approved these changes
Sep 23, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It turns out because
Multiaddr.encapsulatestringifies theMultiaddrit's a suprisingly expensive operation so here we switch the order of ourMultiaddrpipeline around so we filter undialable addresses (e.g. unsupported transports etc) before encapsulating thePeerIdonto aMultiaddrwe'd then just ignore.