Babel supernode optimizations#240
Merged
Merged
Conversation
Supernodes have a lot of routes compared to non-supernodes, and traditional Babel struggles with this on slower nodes. We can optimize various configuration options to help this (as well as improve the code in a few places to be more efficient). The major helper here is to avoid resending routing updates multiple times on supernodes as we can assume the links between them are reliable (not perfect, but that's okay). By default Babel sends these 4 times but on supernodes we can reduce this to just once because we know the update will get through. This massively reduces traffic and overhead.
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
1 participant
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.
Supernodes have a lot of routes compared to non-supernodes, and traditional Babel struggles with this on slower nodes. We can optimize various configuration options to help this (as well as improve the code in a few places to be more efficient). The major helper here is to avoid resending routing updates multiple times on supernodes as we can assume the links between them are reliable (not perfect, but that's okay). By default Babel sends these 4 times but on supernodes we can reduce this to just once because we know the update will get through. This massively reduces traffic and overhead.