News for hackers. Stuff that matters.
Re:Golang's Big Miss on Memory Arenas by pjmlp on Thursday December 11, 2025 @05:03PM (#46237863)
GOGC was introduced in Go 1.5, and I thought the problem was solved.

https://go.dev/blog/go15gc

> Go 1.5’s GC ushers in a future where stop-the-world pauses are no longer a barrier to moving to a safe and secure language. It is a future where applications scale effortlessly along with hardware and as hardware becomes more powerful the GC will not be an impediment to better, more scalable software. It’s a good place to be for the next decade and beyond.

Re:Golang's Big Miss on Memory Arenas by cafxx on Thursday December 11, 2025 @09:18PM (#46240149)
> GOGC was introduced in Go 1.5

yes, that's quite literally what I meant by "GOGC has always been there". 1.5 was released 10 years ago, just 3 years after 1.0.

So to summarize: there is one knob (that has been there from basically the beginning), plus a second one (if you squint hard enough: GOMAXMEM), and absolutely no plans to add further ones, or to add alternative GCs.

Re:Golang's Big Miss on Memory Arenas by pjmlp on Friday December 12, 2025 @01:48AM (#46241504)
That would be since Go exists, literally.
Re:Golang's Big Miss on Memory Arenas by cafxx on Friday December 12, 2025 @07:24PM (#46250702)
The point is that no-one is thinking to add knobs, or allow alternative GCs.