DEV Community

Discussion on: Going Cloud

Collapse
 
jillesvangurp profile image
Jilles van Gurp

You might want to try mosh. This adds a lot of convenience to ssh and allows you to deal with networking issues. Mosh basically uses udp and can keep the session alive as you roam between networks, go on and offline. This is great if you have a laptop. Additionally, it provides a bit better latency and you edit on a local buffer that is synchronized asynchronously. So, you are never blocked on network latency with your key presses. A few years ago when I was working out of coffee shops with generally not great networking, this was a great enabler.

Another thing you could consider is that instead of getting a really big vm on the off chance that you need to do some cpu intensive stuff once in a while, you can just spin up temporary instances and gather the results. Spinning up a huge vm can be expensive but if it only runs for a few minutes the cost becomes quite reasonable. In Amzaon you would do this using spot instances and do some scripting to spin those up and down using aws cli. I'm sure digital ocean has similar stuff. Mostly when doing command line stuff in a terminal you don't actually need a lot of hardware but it is nice to be able to spin it up on demand.

Collapse
 
zeerorg profile image
Rishabh Gupta

As a matter of fact I did try mosh, but found it slow compared to ssh on a reliable network. Will try to go for another type of vm, since tmux sessions sit in RAM they don't eat up a lot of cpu, but buiding huge projects while working do take up cpu cycles in burst, this workload can benefit from a different type of VM.