4 ms·
This isn't measuring "Internet" latency but rather HTTP with all it's overhead, right? When you connect to your favorite MMO, etc., it's doubtful that you're u
by Rimintil 4y ago
This isn't measuring "Internet" latency but rather HTTP with all it's overhead, right?
When you connect to your favorite MMO, etc., it's doubtful that you're using the HTTP protocol to do so.
Still useful, but for one of many "Internet"-based scenarios.
- shepherdjerred 4y agoThe overhead of HTTP should be negligible. I can't imagine it taking even a ms to form an empty GET request TCP probably has higher overhead, but even that is going to be next to nothing unless you've got packet loss
- Rimintil 4y agoHTTP/1.1 and HTTP/2.0 use TCP as the transport, so not only do you have the TCP overhead, but you have the HTTP overhead. There is additional overhead if using HTTPS. traceroute on UN*X uses UDP by default. There is no overhead when using UDP. ICMP Echo, I'm not sure about, but I don't believe it has overhead, but as I said, it is a depriortized and possibly rate-limited by routers.
- shepherdjerred 4y ago> HTTP/1.1 and HTTP/2.0 use TCP as the transport HTTP 1.1 and 2.0 do not require TCP, although that is by far the most common way they are used. What overhead would TCP bring after the three-way handshake on a uncontested stable network without packet loss? I would expect it to be no more than UDP. > traceroute on UN*X uses UDP by default. There is no overhead when using UDP. You are correct. UDP will get you lower numbers, I was more of saying that TCP will not be much worse (maybe within 1ms) under good network conditions.