![]() Note that rsync protocol itself is pretty darn efficient, slightly faster than FTP.ĪES in SSH. So it look like in modern OpenSSH, using AES, it’s a wash which cipher/encryption method you want to use. Ncftpput -m -u ftptest -p ‘XXXXXX’ hp2 /data/ /data/2 NOTE: the file is rm’ed each time at the dest before I do copy. Without specifying encryption, ssh/scp will use the default, which depends on the version of OpenSSH (for this version, the default is aes128-ctr). ![]() Also tested with plain rsync protocol (direct to rsyncd). For comparison purposes, I also timed using plain ole FTP transfer, which mean no encryption and very little system processing and the timing proves that. With scp, I’ll try different encryption, no compression to see how the different encryption affect the transfers. I am going to copy this file from hp1 to hp2, using scp, rsync and ftp. I am using OpenSSH_5.3p1, OpenSSL 1.0.0-fips Tigon ethernet NIC, connected as GigE, full duplex to HP ProCurve 2848 switchģ921247501 Mar 4 08:22 2 (3.8GB) I have two recent vintage HP servers with the following specs.ĭual quad core Intel(R) Xeon(R) CPU E5-2670 0 2.60GHz (8 core, 16 threads total)Ĥ x 3TB, mdadm RAID10, formatted as XFS, mounted noatime,logbufs=8 So I thought I’d do a little bit of testing in a controlled environment. Some people recommend blowfish, others arcfour. I also know about the recommendation to use different type of encryption when transferring files. So doing thing such as rsync (which will use ssh) or even plain scp can be pretty darn slow, especially on large files and on system with old/slow CPU. I’ve known that ssh encryption has an effect on the speed of file xfers.
0 Comments
Leave a Reply. |