fix: concatenate encrypted data length prefix with data before sending #387
Conversation
This file contains 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
Sending lots of tiny buffers kills TCP performance, even with `noDelay` disabled. Sending the encrypted data length along with the data in one buffer increases `@libp2p/perf` throughput with noise+yamux from 300-320 MB/s to 320-340 MB/s
mpetrunic
approved these changes
Nov 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sending lots of tiny buffers kills TCP performance, even with
noDelaydisabled.Sending the encrypted data length along with the data in one buffer increases
@libp2p/perfthroughput with noise+yamux from 300-320 MB/s to 320-340 MB/sFlame graphs showing
Socket._writeGeneric(e.g. writing to the TCP socket) while running the performance test:Before:
After: