3 ms·
> If you have a system that requires predictable latency, go is not the right language for it. Having a garbage collector already make this the case, it is a k
by melodyogonna 7mo ago
> If you have a system that requires predictable latency, go is not the right language for it.
Having a garbage collector already make this the case, it is a known trade off.
- gf000 7mo agoThis may have been practically true for a long time, but as Java's ZGC garbage collector proves, this is not a hard truth. You can have world pauses that are independent of heap size, and thus predictable latency (of course, trading off some throughput, but that is almost fundamental)
- pjmlp 7mo agoNot really, it is a matter of having the right implementation. - https://www.ptc.com/en/products/developer-tools/perc https://www.ptc.com/en/products/developer-tools/perc - https://www.aicas.com/products-services/jamaicavm https://www.aicas.com/products-services/jamaicavm - https://www.azul.com/products/prime https://www.azul.com/products/prime Not all GCs are born alike.
- kevin_thibedeau 7mo agoNim's GC is deterministic when you need it.
- melodyogonna 7mo agoHow so?
- kevin_thibedeau 7mo agoYou can run it for fixed timeslices.