4 ms·
Completely off topic, but regarding SSH over a high latency connection - it's actually remarkably good as long you don't have loss on your link. I'm currently
by ghshephard 13y ago
Completely off topic, but regarding SSH over a high latency connection - it's actually remarkably good as long you don't have loss on your link.
I'm currently working with a client in Singapore that requires that I connect to their data center through a B2B L2L IPSec tunnel that is sourced in California. So, From Singapore, I connect to the VPN concentrator in California, and then from there, connect to the clients site in Singapore.
So, every keystroke that goes to a server approximately 100 meters from me, Starts off in Singapore, crosses the ocean to California, comes back to Singapore, returns back to California, Comes back to Singapore again.
I do this for about 8-10 hours a day - completely workable.
Oh, and the Connection to the internet that my VPN connection rides on is a 3G modem, no less.
- mjallday 13y agoI've done this before too (even down to it being a SG -> CA link!). I think the best practise is to automate. Waiting on individual key presses to be echoed back when there is latency is incredibly frustrating, a slight delay while a shell script runs is completely unnoticeable.
- mikeash 13y agoI think a lot depends on how good of a typist you are. If you can confidently type fast, it's no problem. If you're prone to typos, latency can be unbelievably aggravating.