3 ms·
This is what I thought. Go is primarily targeted at server-side applications, which are almost exclusively running on 64bit hardware/OS. Memory is so cheap now
by riobard 15y ago
This is what I thought. Go is primarily targeted at server-side applications, which are almost exclusively running on 64bit hardware/OS. Memory is so cheap now that it's silly not to have more than 16GB plugged in the chasis.
Then I realized there are many small VPS/EC2 instances with <1GB memory (I have two right now running on 64bit) and there are people who try to squeeze every last bit out of them by going 32bit...
- DisposaBoy 15y agoFWIW I currently have a bot(of sorts) that's been running months constantly crawling, processing(html and images) and logging other sites. It's doing all this in-memory and it peaks at about 34m even with over a hundred active goroutines (70+ are dedicated/never-ending that are usually doing something be it processing or interacting with remote services or external programs)... So I don't see the argument about servers with small amounts of memory. On the issue of improving memory use by going 32bit, I call bullshit on that one.