Comment by jeroenhd
4 days ago
At 40kbps I don't think the latency can be great. Having done SSH over 64kbps when I overran my mobile data subscription, my experience is that modern SSH clients expect more than that to run smoothly.
> Also, slightly meta: What is this web ... app(?)? Looks like a git frontend?
Looking at the source, this seems like a custom-built git frontend, served by a bespoke web server called BEJY (by the same author) it seems.
> At 40kbps I don't think the latency can be great. Having done SSH over 64kbps when I overran my mobile data subscription, my experience is that modern SSH clients expect more than that to run smoothly.
What do these bandwidth numbers have to do with latency?
Even with good latency, most of my connection was taken up by TCP retransmissions at that bandwidth because of an over-eager (standard) SSH client. I can't imagine the TCP stack on an Amiga doing much better in the same scenario.
Not exactly the same scenario of course, but I'd expect you'd need a custom SSH client willing to wait with small enough packets to keep the latency acceptable.
Interesting! Thanks. I had no idea the standard SSH client was so eager.
If the round trip time is dominated by the time taken to encrypt and decrypt packets locally, as seems here, then the speed at which it can complete that is absolutely important for measuring "latency".
Sure. But if it can decrypt at 40 kbps, then this won't be the bottleneck.