aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMirek Kratochvil <exa.exa@gmail.com>2016-06-27 13:08:51 +0200
committerMirek Kratochvil <exa.exa@gmail.com>2016-06-27 13:15:50 +0200
commit4e2e2f253a3462b227301083b2a4f70ebbf13f7e (patch)
tree4b9d78c2c52efcadb44b32527dd27f1efac50e09
parent03c571e99e9cf34419d603e5b6e8a982430caeb2 (diff)
downloadzfs-backup-4e2e2f253a3462b227301083b2a4f70ebbf13f7e.tar.gz
zfs-backup-4e2e2f253a3462b227301083b2a4f70ebbf13f7e.tar.bz2
notice about possible SSH speedups
-rw-r--r--README.md20
1 files changed, 20 insertions, 0 deletions
diff --git a/README.md b/README.md
index 03e4beb..2a2ae58 100644
--- a/README.md
+++ b/README.md
@@ -135,6 +135,26 @@ Check if the environment is the same as when you test the stuff from the command
missing `ssh-agent`, especially the password-protected privkeys. Descriptions
of many workarounds are available around the internet.
+#### Backups pulling soo sloowwwwwww!
+
+There are two possible bottlenecks. We cannot actually cure ZFS's internal
+`send`/`recv` speed (for that, add a multitude of faster disks and caches), but
+we can usually speed up SSH data tranfer a lot. Best advice currently available
+is this: https://gist.github.com/KartikTalwar/4393116
+
+In short, to use the fastest SSH cipher around, add something like this to your
+user's SSH config file:
+
+```
+Host fill.in.some.host
+Ciphers arcfour
+```
+
+Make sure that you understand possible security and compatibility implications
+of this configuration. Specifically, note that some recent SSH installations
+disable arcfour-family ciphers completely for a good reason. If you have `aes`
+CPU extension, aes128-gcm could work quite fast as well.
+
## Disclaimer
Be sure to verify that this software really fits your use-case before you use