[Test conducted 170330]
An attempt to measure the difference using mbuffer/tamp compared
to hipsters latest version of ssh:
pkg list|grep ssh
service/network/ssh 7.2.0.2-2017.0.0.4
=
Send HOST: A vbox vm running hipster on a windows
Do you have any info on just how much of the time difference is just down
to the SSH header overhead?
Do you know how long this takes in comparison to starting an rsyncd server
and sending/receiving via rsync with compression on?
Jon
On 31 March 2017 at 13:29, Harry Putnam wrote:
> [Test condu
Jonathan Adams writes:
> Do you have any info on just how much of the time difference is just down
> to the SSH header overhead?
>
> Do you know how long this takes in comparison to starting an rsyncd server
> and sending/receiving via rsync with compression on?
No to both.
I did do some testin
On Fri, Mar 31, 2017 at 7:29 AM, Harry Putnam wrote:
>
> Sending end (29.7 GB):
>
> root # time zfs send p0/tst.2/isos@170330 | tamp | mbuffer -s 128k -m
> 1000m -O oi0:31337
>
tamp is compression, which takes cpu time. Since your network is gigabit
and you are running substantially below that,
Timothy Coalson writes:
Thanks for the excellent input. I like the details.
[...]
>> root # time zfs send p0/tst.2/isos@170330 | tamp | mbuffer -s 128k -m
>> 1000m -O oi0:31337
>>
>
> tamp is compression, which takes cpu time. Since your network is gigabit
> and you are running substantially
