Re:False Start: Google proposal reduces SSL handshake to sin...
by saranagati on Thursday May 19, 2011 @08:22PM
(#2565909)
the ssl handshake latency isn't why sysadmins don't want to implement everything over https. the reason (or at least 5 years ago when sysadmin was my primary role) is because the additional cpu power it takes to encrypt all the data is huge.
[ Parent
| on HN ]
Re:False Start: Google proposal reduces SSL handshake to sin...
by rdl on Thursday May 19, 2011 @08:27PM
(#2565918)
That's not really true now. CPUs have gotten faster, the speed of light has remained the same, and actually with users on crappy wireless/cell connections (and, increasingly, international), network latency is even more of an issue now.
Re:False Start: Google proposal reduces SSL handshake to sin...
by dangrossman on Thursday May 19, 2011 @08:37PM
(#2565950)
I don't think that's really the case anymore. CPUs have just gotten that much faster. I run a node.js server with https on Linode's cheapest VPS that handles hundreds of requests per second. The server load is at ~0.00 most of the day.