Re:False Start: Google proposal reduces SSL handshake to sin...
by dangrossman on Thursday May 19, 2011 @07:31PM
(#2565763)
Compared to an extra 100-1000 millisecond trip each way to communicate between the browser and the server during the handshake, the CPU time to do the encryption is nothing.
[ Parent
| on HN ]
Re:False Start: Google proposal reduces SSL handshake to sin...
by smithian on Thursday May 19, 2011 @07:37PM
(#2565776)
Where in the world are you getting 1000 ms rtt's? Sat link?
Re:False Start: Google proposal reduces SSL handshake to sin...
by rtomayko on Thursday May 19, 2011 @08:05PM
(#2565857)
Best case you have to do three RTs for a full SSL handshake (without false start anyway), so a RTT of 300ms will bring you pretty close to that 1000ms. We (github.com) certainly have average 1000ms SSL handshakes in Asia -- we're 5 RTs for an SSL handshake presently. It's extremely annoying.
Re:False Start: Google proposal reduces SSL handshake to sin...
by smithian on Thursday May 19, 2011 @09:30PM
(#2566039)
Sure, I manage servers in the US, Japan and Australia so I'm well acquainted with how latency sucks. I was questioning the idea that there was a possibility of "an extra 100-1000 millisecond trip each way" - Taken literally, this would mean up to a 2000ms RTT (1000 ms each way). I get ~230ms RTT between Sydney and NYC, and 320 from Sydney to Hamburg going around the wrong way. for reference, 2000 ms is 74% of the RTT to the moon.
Re:False Start: Google proposal reduces SSL handshake to sin...
by phillmv on Thursday May 19, 2011 @10:41PM
(#2566192)
Oh, I would argue that latency often has no correlation to distance.
Re:False Start: Google proposal reduces SSL handshake to sin...
by smithian on Thursday May 19, 2011 @11:46PM
(#2566309)
When you're talking about SSL handshakes, where else is the latency going to come from?
Re:False Start: Google proposal reduces SSL handshake to sin...
by TeMPOraL on Friday May 20, 2011 @04:10AM
(#2566900)
Poor hardware.
Re:False Start: Google proposal reduces SSL handshake to sin...
by InclinedPlane on Thursday May 19, 2011 @08:21PM
(#2565904)
Not everyone lives within a few hundred miles of the web server they're using.
Re:False Start: Google proposal reduces SSL handshake to sin...
by yuhong on Thursday May 19, 2011 @09:34PM
(#2566050)
Not to mention the WildBlue etc satellite Internet often used in rural areas.
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.
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.