Goland unusable for remote development on small VMs
Answered
I just tried using Goland for developing a Go web application on a EC2 VM with 2GB RAM. It was working pretty well for about an hour, albeit at 85% RAM usage. I was trying Goland due to its ability to gracefully handle Go template syntax, and that was going great!
However, I tried to compile my code with "go run" and RAM spiked to 100%. This RAM spike rendered the VM unusable. I am now trying to reboot the VM to go back to using VS Code, but can't even seem to do that.
In the Goland UI, it said something about remote development being in beta, so I'll give Jetbrains a pass for now. If they are serious about that feature, they must address the performance issues however.
Please sign in to leave a comment.
Hello,
Thanks for trying our Remote Development and sharing our feedback with us.
Please check out the prerequisites to use it: https://www.jetbrains.com/help/idea/2022.2/remote-development-starting-page.html
Is it possible to try it out on a machine with more RAM (at least 4GB)?
It will be about a week before I'm developing again, but I'll try it and report back.
For what it's worth, Goland's highlighting of Go HTML templates was great. Definitely superior to any VS Code plugin I've found so far.
How much RAM does Goland's server need to run? About a GB? Is it just a Java program running on the host?
It depends on the project size in the first place, I'd say the following gradation:
- Small project: ~2GB.
- Medium project: ~3-4GB.
- Large project: 4GB+.
Please keep in mind that besides GoLand server different things can increase memory consumption, e.g. building process of your application.