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.
[ Parent
| on HN ]
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?