same! how do you deal with cloudtop latency though? sometimes my neovim is very slow and laggy because of the remote connection / network file system
same! how do you deal with cloudtop latency though? sometimes my neovim is very slow and laggy because of the remote connection / network file system
Cloudtop to run builds, g4 commands, etc., and srcfs / srcfsn to actually write code. (caveat: I have never used neovim, so I don't know if that is different).
Mosh instead of ssh. Works well enough for as long as it works.
Road warrior even supports it.
But i keep going back to regular ssh or shpool with roadwarrior.
Spin up one in the US central region instead of an instance near your satellite office. The bottleneck is usually not your shell connection to the instance but the connections from the instance to all the infrastructure that's mainly based in the US.
I use a workstation specifically to improve latency. Needed to get approval at some point to get a refresh though.
like a workstation under your desk? is the latency bad when you remote access it not in the office?
Yeah, under my desk. I rarely remote which is a good excuse for me to disconnect from work anyways.
Ever tried SSH'ing via "Mosh"? https://mosh.org
I have a (Google-issued) desktop in the same city I live in, so the latency is not so bad.
I will say that the latency of the filesystem is a different problem. Most of the google filesystem tooling is not built for command line tools that expect to index large subsets of the filesystem at once.