From 2f7d842f004f2d7146b95a53012f9627f578b6ec Mon Sep 17 00:00:00 2001 From: DatuX Date: Tue, 4 Apr 2023 15:43:43 +0200 Subject: [PATCH] Updated Performance (markdown) --- Performance.md | 29 +++++++++++++++-------------- 1 file changed, 15 insertions(+), 14 deletions(-) diff --git a/Performance.md b/Performance.md index 49c7d44..6e77131 100644 --- a/Performance.md +++ b/Performance.md @@ -17,6 +17,21 @@ Host * Thanks @mariusvw :) +### Direct TCP network transfer + +If ssh-encryption performance is still too slow for your use-case, you can do a direct unencrypted transfer via tcp ip: + +Use something like this: +```console +zfs-autobackup ... --send-pipe "nc server_name 8023" --recv-pipe "nc -l -p 8023" +``` + +This will pipe the data through netcat on the specified port. (You can use any transfer program you want this way) + +Note that only the actual transfer of the ZFS-data during zfs send/recv is done via this, it still requires SSH for all the other stuff. + +Also see: https://github.com/psy0rz/zfs_autobackup/issues/15#issuecomment-1043753454 + ## Buffering and compression Also it might help to use the `--buffer` option to use IO buffering during the data transfer. @@ -72,17 +87,3 @@ More info: https://en.wikipedia.org/wiki/Scalable_TCP (thanks @xrobau) -## Direct TCP network transfer - -If ssh-encryption performance is too slow for your use-case, you can do a direct unencrypted transfer via tcp ip: - -Use something like this: -```console -zfs-autobackup ... --send-pipe "nc server_name 8023" --recv-pipe "nc -l -p 8023" -``` - -This will pipe the data through netcat on the specified port. - -Note that only the actual transfer of the ZFS-data during zfs send/recv is done via this, it still requires SSH for all the other stuff. - -Also see: https://github.com/psy0rz/zfs_autobackup/issues/15#issuecomment-1043753454