4 ms·
In my experience, you only need to start looking at GC parameters once you hit a certain scale. For the majority of services you'll be writing, especially in a
by seer-zig 4y ago
In my experience, you only need to start looking at GC parameters once you hit a certain scale. For the majority of services you'll be writing, especially in a small team, you don't have to worry about them. G1GC is really good, and if you need low latency, you have ZGC and Shenandoah.
We've seen the hoops that people had to jump through to get golang GC to work properly once they hit a certain scale.
- mosdl 4y agoThe main reason we chose Go was compilation speed since our product would need to quickly compile and generate something that is fast to startup, and Graal was just too slow when we prototyped things. The GC benchmarks we did showed that Go would work as well, so we begrudgingly moved to it.