Re:The 64 Milliseconds Manifesto
by toast0 on Tuesday September 24, 2019 @04:06PM
(#21064061)
Depending on how your environment is configured...
Curl will do one round trip to your resolv.conf configured resolver
Then you have one round trip for tcp.
Then another for TLS hello (presuming TLS 1.3 or false-start)
Then one last round trip for HTTP.
Assuming cached DNS, you need a ping to the server of about 21ms to get content via https in 64ms. And that's assuming you can get enough content for a screens worth in the initial congestion window (10ish packets, so let's say 15kb). Good luck!
Oh, and my DSL connection adds at least 20ms to the path, and that's not unusual.
Curl will do one round trip to your resolv.conf configured resolver
Then you have one round trip for tcp.
Then another for TLS hello (presuming TLS 1.3 or false-start)
Then one last round trip for HTTP.
Assuming cached DNS, you need a ping to the server of about 21ms to get content via https in 64ms. And that's assuming you can get enough content for a screens worth in the initial congestion window (10ish packets, so let's say 15kb). Good luck!
Oh, and my DSL connection adds at least 20ms to the path, and that's not unusual.