Cryptoxide perf (SHA2 / Blake2)

2021-01-17T00:00:00+00:00

Related to some engine rewrite and SSE, AVX, AVX2 cpu optimisation I did last year on cryptoxide</a> :</p>

SHA2 optimisation</a></li>
Blake2 optimisation</a></li> </ul> </span>
History of cryptoxide §</a> </h2>
Cryptoxide is a fork of the initial rust-crypto</a> one-stop cryptography package that went unmaintained.</p>
In 2018, we needed a pure rust version to construct rust-wasm based web-applications when this use case was in its infancy; rust-crypto was an interesting starting point, as all the algorithms were written in pure rust, and it was also easier to construct something than the exploded version which would have required lots more time to port.</p>
Many other cryptographic packages are now wasm friendly also.</p>
Benchmarks setup§</a> </h2>
- ring: 0.16.19</li> </ul>
  The benchmark code itself consist of benchmarking few time the main costly part of each algorithm over a 10 megabytes array and taking the average of the run. It's possible that the number reported could be buggy, but it should be consistently buggy, so here we're more interested by the relative values than the absolute values.</p>
  This benchmark is only looking at the function I was interested about also, thus only compare Sha256, Sha512, Blake2b and Blake2s.</p>
  Finally benchmarks should always be taken with a grain of salt, as different cpu and environment can lead to different results.</p>
  To play with the benchmark on your own machine, have a look at rcc</a></p>
  Raw numbers §</a> </h2>
  Let's start with the raw number in release mode; This show the average (lower better) with standard deviation (the lower, the better for reliability of benchmark), and the speed of processing (higher better):</p>
  Using the default target_cpu:</p>
  Algorithm</th> Crate</th> Avg(ms)</th> Std Dev(ms)</th> Speed(mb/s)</th></tr></thead>
  
  blake2b</td> cryptoxide</td> 10.18</td> 0.174</td> 981</td></tr>
  blake2b</td> blake2</td> 10.28</td> 0.260</td> 972</td></tr>
  blake2s</td> cryptoxide</td> 15.97</td> 0.264</td> 625</td></tr>
  blake2s</td> blake2</td> 17.07</td> 0.150</td> 585</td></tr>
  sha256</td> cryptoxide</td> 30.51</td> 0.220</td> 327</td></tr>
  sha256</td> sha2</td> 35.66</td> 0.277</td> 280</td></tr>
  sha256</td> ring</td> 19.17</td> 0.293</td> 521</td></tr>
  sha512</td> cryptoxide</td> 20.86</td> 0.319</td> 479</td></tr>
  sha512</td> sha2</td> 21.10</td> 0.422</td> 473</td></tr>
  sha512</td> ring</td> 13.29</td> 0.296</td> 752</td></tr> </tbody></table>
  Using the native target_cpu target_cpu=native</code>:</p>
  Algorithm</th> Crate</th> Avg(ms)</th> Std Dev(ms)</th> Speed(mb/s)</th></tr></thead>
  
  blake2b</td> cryptoxide</td> 6.72</td> 0.229</td> 1486</td></tr>
  blake2b</td> blake2</td> 9.95</td> 0.388</td> 1004</td></tr>
  blake2s</td> cryptoxide</td> 11.27</td> 0.232</td> 886</td></tr>
  blake2s</td> blake2</td> 17.23</td> 0.136</td> 580</td></tr>
  sha256</td> cryptoxide</td> 20.71</td> 0.243</td> 482</td></tr>
  sha256</td> sha2</td> 28.31</td> 0.365</td> 353</td></tr>
  sha256</td> ring</td> 19.74</td> 0.283</td> 506</td></tr>
  sha512</td> cryptoxide</td> 17.13</td> 0.184</td> 583</td></tr>
  sha512</td> sha2</td> 17.50</td> 0.339</td> 571</td></tr>
  sha512</td> ring</td> 13.17</td> 0.133</td> 759</td></tr> </tbody></table>
  In Graphs§</a> </h2>
  Putting in graphical form, comparing the default and native runs:</p>

Typed Chronicles

Cryptoxide perf (SHA2 / Blake2)

Benchmarks setup§</a> </h2> cpu: 3.6 GHz 8-Core Intel Core i9 (I9-9900K)</li> rust compiler: stable 1.49</li> cryptoxide: 0.3.0</li> rust-crypto: blake2 0.9.1, sha2 0.9.1</li>