12 requests per second: A realistic look at Python web frameworks

Re:12 requests per second: A realistic look at Python web fr... by toast0 on Friday February 19, 2021 @03:38AM (#26190918)

> Signing, verification, and key exchange are quite expensive. ECC doesn't help server-side; it mostly reduces client-side verification costs.

I don't think that's right. Cloudflare's blog [1] says they can do about 9.5x the handshakes/sec with ECDSA at 256-bits vs RSA at 2048. Verification for ECDSA signatures are somewhat slower, but it's usually an acceptable tradeoff to make clients do a bit more work so that servers do a lot less.

I agree though, at 12 RPS, TLS isn't the bottleneck.

[1] https://blog.cloudflare.com/ecdsa-the-digital-signature-algo...

[ Parent | on HN ]

Re:12 requests per second: A realistic look at Python web fr... by wahern on Friday February 19, 2021 @04:30AM (#26191188)

Ah, you're right. 1) I got it backwards, verification is much faster with RSA, so RSA is better for clients). 2) I was testing libressl (macOS, OpenBSD), where signing speeds between rsa2048 and ecdsap256 are nearly identical (Core i5, M1, AMD GX-412T), whereas with OpenSSL (AMD EPYC) ecdsap256 is faster (30x advantage to ecdsap256 actually, as compared to 4x verification advantage to RSA). Though, the magnitudes here seem to be sensitive to optimization effort.

[ Parent | on HN ]