4 ms·
On modern internet, with some assumption, you can get to like 2x faster(in my case) when sending data over an *already establised* connection. Example: A full
by kureikain 5y ago
On modern internet, with some assumption, you can get to like 2x faster(in my case) when sending data over an *already establised* connection.
Example:
A full fresh HTTP connect from client to first byte take ~400ms(I'm in the US the server is in Europe). This includes: resolve dns, open tcp connection, ssl handshake etc...
But if the connection is already establish, it only takes ~200ms to first byte.
If I deployed the server in the same region, say US customer <-> US server, this came down to 20ms...
That means, it's good enough.
Not super ideal but It's a trade-off we're willing to make.
- janekm 5y agoLiveView (I think) already achieves this optimisation as both the initial content and any future updates come over the same persistent websocket connection.