3 ms·
I still run into technical people very regularly that believe HTTPS is a big performance hit. I'm not sure what's perpetuating that myth (present day myth, 15 y
by adventured 12y ago
I still run into technical people very regularly that believe HTTPS is a big performance hit. I'm not sure what's perpetuating that myth (present day myth, 15 years ago it was true). I build everything side-wide HTTPS, and have rarely run into a situation where it caused even a 1% performance loss, and at those levels it's simply irrelevant in comparison to the benefit.
- belorn 12y agoIn 2010, google switched to https for gmail and publishes the performance cost for it. On our production frontend machines, SSL/TLS accounts for less than 1% of the CPU load, less than 10 KB of memory per connection and less than 2% of network overhead. Many people believe that SSL/TLS takes a lot of CPU time and we hope the preceding numbers (public for the first time) will help to dispel that.
- Dylan16807 12y agoWas it true 15 year ago? Are you sure?
- acdha 12y agoYes. Remember that 15 years ago doesn't mean only that processors were much slower but also that you don't have the heavily-optimized software implementations and hardware acceleration for the most common implementations. You can run OpenSSL today on an embedded processor which might appear to be as slow as a 90s server processor but it's still likely to have things like AES support in the CPU, an optimized bignum library, tuned assembly implementations for the most common algorithms and at least the very least the compilers in use now generate much better code. I'd be surprised if you wouldn't see a significant benefit taking some 90s crypto code and compiling it with a current version of clang/gcc.
- Dylan16807 12y agoWell I've done some research to get exact numbers. The 2010 Google announcement that gets cited a lot talks about cores capable of doing 1500 handshakes per second (1024 bit RSA), and only needing 1% of CPU power. I found a couple sources claiming that a Pentium 3 should be capable of 200 handshakes per second max (1024 bit RSA), and also that it could hash over 50Mbps with 3DES or well over 100 with RC4-MD5. I can't find if those Google servers had AES acceleration, but the chips with it had only just come out. So looking at the year 2000: Pentium 3 is about 10x slower at handshaking, and somewhere around 10x[1] slower at encrypting depending on algorithm. So if you can spare 10-20% CPU, I don't see any major problems with going full-SSL. [1] This one can vary more depending on exactly what you compare. Could be close to equal speed if you accept a worse algorithm for 2000, and don't have brand new AES-NI chips in 2010. Could be a huge multiplier between 3DES and AES-NI, but your server doesn't need a gigabyte per second of SSL traffic.