Performance compared to crypto.createSign ecdsa-with-SHA1

[jpillora]

Hi @indutny, have you tested the performance of signing and verifying with node's crypto (ecdsa-with-SHA1)? I'm curious as to whether the vanilla JS solution could get a leg up on OpenSSL since it doesn't have to cross the JS-C++ bridge?

[indutny]

Just pushed an update to benchmark:

Benchmarking: sign
elliptic#sign x 407 ops/sec ±0.80% (155 runs sampled)
sjcl#sign x 53.25 ops/sec ±0.83% (137 runs sampled)
openssl#sign x 1,548 ops/sec ±0.63% (193 runs sampled)
------------------------
Fastest is openssl#sign
========================
Benchmarking: verify
elliptic#verify x 157 ops/sec ±0.78% (161 runs sampled)
sjcl#verify x 45.63 ops/sec ±0.68% (118 runs sampled)
openssl#verify x 1,400 ops/sec ±0.41% (195 runs sampled)
------------------------
Fastest is openssl#verify
========================

[jpillora]

Thanks Fedor

So I original made eccjs so web clients could participate in the same
ecosystem as the server clients. Though looks I was right to jump ship
from eccjs. Just using plain TLS now.

If one really needed ecc in the browser, maybe asm.js could help?

On Monday, June 9, 2014, Fedor Indutny notifications@github.com wrote:

Closed #2 #2.

—
Reply to this email directly or view it on GitHub
#2 (comment).

[indutny]

asm.js could help indeed. Right now I'm thinking about making bn.js use typed arrays.