If you're having to debug code, VSCode has really good integrations for running on your remote server. Unless you're already very familiar with vim, it's going to be quicker to set this up.
Ensure you've got rsync experience - no one wants to include venv when pulling your changes back from the remote side.
Run the image you're using remotely locally via docker first. Check your code works, you don't want to be messing around with fixes while your GPUs sit idle.
If you're running compiled code, check the CPU architecture. I wasted a day debugging a fault that was due to compiling starspace on a build server that had different architecture to our remote server.
Lifaux t1_j957q53 wrote
Reply to [D] Things you wish you knew before you started training on the cloud? by I_will_delete_myself
If you're having to debug code, VSCode has really good integrations for running on your remote server. Unless you're already very familiar with vim, it's going to be quicker to set this up.
Ensure you've got rsync experience - no one wants to include venv when pulling your changes back from the remote side.
Run the image you're using remotely locally via docker first. Check your code works, you don't want to be messing around with fixes while your GPUs sit idle.
If you're running compiled code, check the CPU architecture. I wasted a day debugging a fault that was due to compiling starspace on a build server that had different architecture to our remote server.
Tmux is a godsend.