blake2s-js

>My pure JavaScript implementation of blake2s (which is approximately half the speed of parallelized sp variant) on 2.6 GHz Core i5 hashes at 170 MiB/s. If I recompile blake2sp with "/O2" optimization, it improves to 171MB/sec. I ran tests with "/Od" optimizations disabled because the default Crypto++ library project has optimizations disabled when it makes the lib file. Therefore, every hash had no optimizations to keep the comparisons apples to apples. I see your Javascript code of BLAKE2 on github so I'll try it and compare. (https://github.com/dchest/blake2s-js) >Also, there is no reason to use such large buffer sizes, I suspect this only makes benchmarks more unreliable. I chose 500MB because I wanted the fastest hashes (CRC32, MD5) to take at least 1 second and many data sizes I want to hash will be 10GB+.

If hash computation in Javascript is a crucial bottleneck, there are better choices than SHA1-- like BLAKE2s, which is designed to be fast on 32-bit platforms. If collisions aren't a huge concern, something like SipHash is also possible. https://blake2.net/ https://github.com/dchest/blake2s-js https://131002.net/siphash/