{"id":2255,"date":"2016-06-01T18:28:26","date_gmt":"2016-06-01T16:28:26","guid":{"rendered":"http:\/\/possiblelossofprecision.net\/?p=2255"},"modified":"2021-05-15T11:46:37","modified_gmt":"2021-05-15T09:46:37","slug":"openssh-cipher-performance","status":"publish","type":"post","link":"https:\/\/possiblelossofprecision.net\/?p=2255","title":{"rendered":"OpenSSH cipher performance"},"content":{"rendered":"

The achievable speed of copying a file with OpenSSH (e.g. with scp<\/code>) will depend on quite a few different factors such as CPU speed, CPU architecture, Network throughput, OpenSSH implementation, OS, hard drive speed, etc. But how much of a difference does choosing a different cipher algorithm make? And what’s the fastest OpenSSH cipher algorithm?<\/p>\n

Turns out, there’s no simple answer to this question, since most of the factors that influence the transfer speed can be ruled out, but the results will at least depend on the hardware platform and OpenSSH version. There’s quite a few different benchmarks out there, e.g. for the Bifferbord<\/a>, E5 xeon CPUs<\/a> or different consumer grade CPUs and ARM processors<\/a>. But since the results are so heavily platform dependent, it’s a good idea to run your own benchmark on the particular platform you are interested in. So here’s another data point for an Intel Xeon E5-2640<\/a> and OpenSSH 6.9p1 (OpenSSL 1.0.1k).<\/p>\n

The test setup is quite similar to the one described at blog.famzah.net<\/a>. The bash script used to produce the data is:<\/p>\n

\r\nfor cipher in aes128-ctr aes192-ctr aes256-ctr arcfour256 arcfour128 aes128-cbc 3des-cbc blowfish-cbc cast128-cbc aes192-cbc aes256-cbc arcfour\r\ndo\r\n   echo "$cipher"\r\n   for try in 1 2\r\n   do\r\n      scp -c "$cipher" \/tank\/fs\/testfile.img root@localhost:\/tank2\/fs\/\r\n   done\r\ndone\r\n<\/pre>\n
The test file consists of 5GiB<\/strong> random data. Both the source and target file system are RAM backed<\/a> to remove the influence of HDD read and write speeds. In addition to that, the test file is written to localhost to ensure that network speed, load and NIC drivers do not influence the test results.<\/p>\n
\"\"<\/a>
SCP file transfer speed<\/p><\/div>\n
The results clearly show, that the Xeon’s AES instruction set is used. Most modern x86 CPUs<\/a> do come with this extension these days.<\/p>\n
While this data clearly suggests, that AES encryption<\/a> is the faster cipher OpenSSH cipher (if there is hardware support for it as in this case), copying large amounts of data with scp<\/code> is not a particularly interesting use case. Sending big streams of data through a pipe into ssh, as you do when you send and receive ZFS snapshots<\/a> over ssh, is a very common application. For benchmarking reasons, sending actual ZFS snapshots is not ideal, since ZFS takes some extra time to check the receiving file system (and its snapshots) before starting the sending process. So here’s an altered script that should tell us, what the fastest cipher for that particular use case is:<\/p>\n
\r\nfor cipher in aes128-ctr aes192-ctr aes256-ctr arcfour256 arcfour128 aes128-cbc 3des-cbc blowfish-cbc cast128-cbc aes192-cbc aes256-cbc arcfour\r\ndo\r\n   echo "$cipher"\r\n   for try in 1 2\r\n   do\r\n      cat \/tank\/fs\/testfile.img | pv | ssh -c "$cipher" root@localhost "cat - > \/dev\/null"\r\n   done\r\ndone\r\n<\/pre>\n
The only difference can be found in the highlighted line: Instead of using scp<\/code> the file is now piped directly into ssh and discarded on the receiving side. Again, the 5GiB<\/strong> test file lives on a RAM backed file system and the transfer is done to localhost.<\/p>\n
\"\"<\/a>
SSH piped file transfer speed<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"
The achievable speed of copying a file with OpenSSH (e.g. with scp) will depend on quite a few different factors such as CPU speed, CPU architecture, Network throughput, OpenSSH implementation, OS, hard drive speed, etc. But how much of a difference does choosing a different cipher algorithm make? And what’s the fastest OpenSSH cipher algorithm? Turns out, there’s no simple… Read more »<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[76,15,75],"class_list":["post-2255","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-linux","tag-ssh","tag-zfs"],"_links":{"self":[{"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=\/wp\/v2\/posts\/2255","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2255"}],"version-history":[{"count":14,"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=\/wp\/v2\/posts\/2255\/revisions"}],"predecessor-version":[{"id":2271,"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=\/wp\/v2\/posts\/2255\/revisions\/2271"}],"wp:attachment":[{"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2255"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2255"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/possiblelossofprecision.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2255"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}