Hacker News Reader

Comment by c0l0 | Hacker News Reader

100ms TLS session setup time with RTT <15ms seems rather unacceptable to me.

Can you provide the timings this command produces for you?

    curl -s -w 'TCP=%{time_connect} TLS=%{time_appconnect} ALL=%{time_total}\n' https://YOUR_REMOTE_HOST_GOES_HERE -o /dev/null

That should provide an easy to use ruler to compare measurements.

View on HN

I was bored so I tested this on AWS from EC2 instance to ELB HTTPS load balancer (in the same VPC), and I got about 5-10ms time_total as reported by curl. So that sort of gives a baseline on what TLS latency can be when network is fast.

I've written a simple bash script based on your one liner: https://ybin.me/p/53f0aa4e1204b470#c561Frz6wpKkfvsTklDdZFOer...

Here is the output for 100 reqs: https://ybin.me/p/1e68f80f6910ba0d#USqFo3Loksx5rHQIe16NHp299...

what are the output units? seconds, or ms? my results make most sense if it's seconds:

    $ curl -s -w 'TCP=%{time_connect} TLS=%{time_appconnect} ALL=%{time_total}\n' https://<my-domain>/ -o /dev/null

    TCP=0.021106 TLS=0.052928 ALL=0.143908

All of curl's --write-out values that begin with `time_` are given in seconds.

thank you

Reply on news.ycombinator.com