use ssh compression and a ssh-cipher that enables AES-NI #17
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
If the transfer rate is limited by
- network-bandwidth, enable SSH stream compression
- ssh/sshd cpu load, switch the ssh-cipher to a one that utilizes
hardware-accelerated crypto (like x86-aes-ni)
vog
force-pushed
the
master
branch
2 times, most recently
from
cc531de
to
a6b0217
Compare
|
@glaweh Did you make performance measurements to verify that these SSH options actually do what they are supposed to do? If so, what speedup (roughly) did you measure? |
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.
If the transfer rate is limited by
hardware-accelerated crypto (like x86-aes-ni)