Crypto timings

[Kurt Roeckx]

On Sun, Jan 29, 2017 at 09:09:56PM +0000, Greg Rubin wrote:
> Mind running the timings with the legacy interfaces as well?  We may
> determine that the speed benefits are outweighed by the risks and
> complexities of an older API, but it would be good to have the data so we
> can make an informed decision.
> 
> https://www.openssl.org/docs/man1.0.2/crypto/md5.html
> https://www.openssl.org/docs/man1.0.2/crypto/sha.html

On an i5-2500 @ 3.3 GHz, with openssl 1.0.1t:
openssl speed md5 sha1:
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes
md5              57722.54k   170970.22k   379334.74k   545487.19k   625227.09k
sha1             67990.28k   189759.61k   407470.34k   571764.74k   649565.53k

openssl speed -evp md5 sha1:
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes
sha1             67922.42k   189184.53k   407347.80k   571157.85k   649428.99k
md5              69949.09k   196024.75k   407446.02k   561352.70k   628984.49k

(Note that it changed the order of sha1 and md5, but I've made the order the same)

Instead with the 1.1.0d version:
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
md5             108391.99k   257522.09k   468072.79k   586233.51k   633440.94k   636813.31k
sha1            105271.81k   253953.34k   485931.43k   629915.65k   688802.47k   693933.40k

vs:
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
md5              56006.90k   165390.34k   372050.26k   541776.48k   626789.03k   631794.35k
sha1            106968.33k   259511.66k   491601.07k   631022.93k   690307.07k   694250.15k

(I guess I need to talk to Andy about the md5 results on 1.0.1d with -evp.)

on Opteron 6128 @ 2 GHz with 1.0.2j:
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes
md5              31425.80k    94665.83k   224058.91k   338552.83k   399575.72k
sha1             33109.40k    92994.65k   198053.12k   275247.45k   311880.36k

vs:
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes
md5              37516.02k   108757.61k   241711.45k   348012.54k   401257.81k
sha1             32777.98k    92063.98k   197674.24k   274422.10k   311388.84k


On an i5-5200U @ 2.2 GHz with 1.0.1t:
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes
md5              49263.92k   143836.15k   316048.30k   455134.21k   523655.11k
sha1             59227.40k   167068.95k   361932.12k   521637.89k   614361.77k

vs:
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes
md5              60008.47k   165981.64k   336796.42k   467899.39k   517005.01k
sha1             58571.46k   166523.95k   360590.29k   521334.10k   616609.11k


On a armel kirkwood (600 MHz?) with 1.0.1t:
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes
md5               3728.56k    13010.79k    36292.53k    66204.26k    86466.90k
sha1              3820.86k    11280.40k    25024.39k    35906.32k    41140.50k

vs:
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes
md5               4688.57k    15861.30k    41397.71k    70352.28k    87673.64k
sha1              3837.16k    11275.29k    24967.28k    35942.06k    41140.83k


Plenty of other boxes I could run this on.


Kurt