Re: ssh None cipher

On 2014-10-18 13:21, Freddie Cash wrote:
> On Oct 18, 2014 3:54 AM, "Mark Martinec" <Mark.Martinec+freebsd_at_ijs.si>
> wrote:
>>
>> If the purpose of having a none cipher is to have a fast
>> file transfer, then one should be using  sysutils/bbcp
>> for that purposes. Uses ssd for authentication, and
>> opens unencrypted channel(s) for the actual data transfer.
>> It's also very fast, can use multiple TCP streams.
> 
> That's an interesting alternative to rsync, scp, and ftp, but doesn't help
> with zfs send/recv which is where the none cipher really shines.
> 
> Without the none cipher, SSH becomes the bottleneck limiting transfers to
> around 400 Mbps on a gigabit LAN. With the none cipher, the network becomes
> the bottleneck limiting transfers to around 920 Mbps on the same gigabit
> LAN.
> 
> This is between two 8-core AMD Opteron 6200 systems using igb(4) NICs.
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> 

Actually, looking into it, the bbcp command can support a pipe at each
end instead of files, so you can actually do a zfs send | zfs receive
via bbcp, and use multiple concurrent connections, to get around TCP
window stuff when going transatlantic

I am going to be trying it out shortly.

Note: the other big improvement in newer ssh is the HPN stuff, that is
switched on since 9.2 I think.

-- 
Allan Jude