Closed ericmorand closed 6 years ago
OS, Browser, Version? Did you check it with other browsers?
@jochenonline, no browser, server-side, nodejs 9.8.0.
Why don't you use the internal crypto functions?
https://nodejs.org/api/crypto.html#crypto_crypto_createhash_algorithm_options
@jochenonline, I do. But I was assuming your implementation would be faster.
It was... until 2014 when Crome and FF released WebCrypto API support.
@ericmorand : asmcrypto is asm.js / WebCrypto is binary. So on server side any binary implementation will beat asmcrypto.
Ooooh, sorry, I missed that part. Thanks for your clarification and patience.
Hi.
I made a little benchmark to compare asmcrypto with two other popular node.js crypto libs and my tests show that it's way slower than them, which is unexpected considering that performance is the main point of your lib:
On my system:
asmcrypto: ~650ms sha.js: ~370ms crypto: ~300ms
Is there something I'm doing wrong here? I'm already thinkng that other crypto libs are extremely slow (for comparison, PHP hash function execute that test in ~70ms - yes, seventy!) and was hoping asmcrypto would solve that issue.