22 points shellpipe 3 hours ago 5 comments

octoberfranklin 20 minutes ago | parent

Yet another reason why "no runtime" is such a huge advantage.

pizlonator 20 minutes ago | parent

Is there a reason why Go isn’t using on the fly GC, where there’s no STW at all?

klodolph 10 minutes ago | parent

What I found when I searched for "on the fly" is this: https://github.com/mthom/on-the-fly-gc — it looks like it has pauses, from the docs.

In general when you tune knobs for GC, you pay for benefits in one area with sacrifices in another. Two big knobs to turn are pause latency and throughput. You probably wouldn’t want to go full “optimize for latency” because you’d end up with poor throughput. Also vice versa. Java’s reputation for poor GC performance is partly due to historical defaults that tune it for throughput.

Go’s GC is already a “concurrent mark-sweep garbage collector” and already has “extremely low mutator pause times, on the order of tens of microseconds”. It sounds like on-the-fly is just a different flavor of what Go already has.

truth_seeker 15 minutes ago | parent

What is stopping the author to use latest version of Go and Linux Kernel ?