582377 - Establishing SSL connections is slow

Status: RESOLVED WORKSFORME

(mozilla.org Graveyard :: Server Operations, task)

Description

[Jeff Balogh (:jbalogh)]

Getting an SSL connection to AMO takes 1.2 seconds.  Amazon takes 110ms.  Google takes 80ms.

I tested each of these once, so they're most certainly statistically valid.

Comment 1

[Jeremy Orem [:oremj]]

How are you testing?

Comment 2

[Jeff Balogh (:jbalogh)]

I'm looking at the Resource Tracking panel in Chrome.

Comment 3

[Jeremy Orem [:oremj]]

Gomez is showing 0.015-0.030 seconds establishing an SSL connection.

Comment 4

[Jeremy Orem [:oremj]]

Hmm, I'm not able to narrow down by ssl connection time in chrome. I only see latency and page load time.

Comment 5

[Jeff Balogh (:jbalogh)]

I have 6.0.472.4.  I guess it's the dev channel.

http://www.webpagetest.org/result/100727_1YG4/1/details/ shows 545ms for SSL.

If gomez is always testing from the same location, won't some pieces be cached?

Comment 6

[Jeremy Orem [:oremj]]

It tests from a bunch of locations. I assume they don't cache as that would defeat the purpose of their service.

Comment 7

[Jeff Balogh (:jbalogh)]

(In reply to comment #6)
> It tests from a bunch of locations. I assume they don't cache as that would
> defeat the purpose of their service.

That connection time in comment 3 is astoundingly fast.

Comment 8

[Jeremy Orem [:oremj]]

I think webpagetest.org is slow:

http://www.webpagetest.org/result/100727_1YGT/1/details/#request1

that shows google at 260ms.

Comment 9

[Jeremy Orem [:oremj]]

[oremj@boris ~]$ time (echo "GET /"  | openssl s_client -connect addons.mozilla.org:443 > /dev/null 2> /dev/null) 

real	0m0.039s
user	0m0.021s
sys	0m0.010s
[oremj@boris ~]$ time (echo "GET /"  | openssl s_client -connect addons.mozilla.org:443 > /dev/null 2> /dev/null) 
real	0m0.039s
user	0m0.021s
sys	0m0.008s
[oremj@boris ~]$ time (echo "GET /"  | openssl s_client -connect addons.mozilla.org:443 > /dev/null 2> /dev/null) 
real	0m0.040s
user	0m0.020s
sys	0m0.006s
[oremj@boris ~]$ time (echo "GET /"  | openssl s_client -connect addons.mozilla.org:443 > /dev/null 2> /dev/null) 
real	0m0.039s
user	0m0.021s
sys	0m0.007s

Comment 10

[Jeremy Orem [:oremj]]

All of those are under .04 seconds and also are showing the time needed to start up echo and openssl.

Comment 11

[Wil Clouser [:clouserw]]

I consistenly get just over 1s to AMO with that command off my cable.  I get .8s to secure.google.com.  Not much different.

Comment 12

[Jeremy Orem [:oremj]]

That's also measuring latency. I'm in the local network, so latency is basically 0.

Comment 13

[Jeremy Orem [:oremj]]

From my laptop:

shiny:~ oremj$ time (echo "GET /"  | openssl s_client -connect addons.mozilla.org:443 > /dev/null 2> /dev/null)

real	0m0.159s
user	0m0.005s
sys	0m0.005s
shiny:~ oremj$ time (echo "GET /"  | openssl s_client -connect addons.mozilla.org:443 > /dev/null 2> /dev/null)

real	0m0.174s
user	0m0.005s
sys	0m0.005s


and google:

shiny:~ oremj$ time (echo "GET /"  | openssl s_client -connect www.google.com:443 > /dev/null 2> /dev/null)

real	0m0.196s
user	0m0.004s
sys	0m0.005s
shiny:~ oremj$ time (echo "GET /"  | openssl s_client -connect www.google.com:443 > /dev/null 2> /dev/null)

real	0m0.188s
user	0m0.004s
sys	0m0.005s
shiny:~ oremj$ time (echo "GET /"  | openssl s_client -connect www.google.com:443 > /dev/null 2> /dev/null)

real	0m0.182s
user	0m0.004s
sys	0m0.005s