3 ms·
2.5s is the minimum roundtrip. Add server and satellite hops and you get something closer to 3s minimum. Every time.
by anticensor 6y ago
2.5s is the minimum roundtrip. Add server and satellite hops and you get something closer to 3s minimum. Every time.
- justinclift 6y agoThanks. Sounds like it'd be workable as a backup target then, but would probably suck being the primary place to grab source code. That being said, maybe it would be ok as a primary location if there are more localised caches (eg lower response times) commonly available.
- ColanR 6y agoIt's git - what do you need low-latency for? Download directories, trees, as the initial requests, then send a second request for the source code you want to download. Then the bottleneck is download speed instead of latency.
- justinclift 6y agoFor just git, sure. For a web application to present it (eg Gitea, GitLab, etc), then the lower latency would be helpful. ;)
- ColanR 6y agoeh, web applications are overrated. :)
- m4rtink 6y agoNot a problem for Git or even PR workflow then.
- anticensor 6y agoIt would not be an issue even in the Earth-Mars case, where the roundtrip latency is 20m-1h15m depending on the time.
- justinclift 6y agoWell, you probably wouldn't want to try using standard TCP connections with that. ;)
- m4rtink 6y agoI wonder how this will work out in practice. Funny thing old pre-Internet protocols migh even work out of the box in this case. Interplanetary email & newsgroups! :-)