Go now has memory regions, an automatic form of arenas: https://go.googlesource.com/proposal/+/refs/heads/master/design/70257-memory-regions.md#annotated-exampl

Go now has memory regions, an automatic form of arenas: https://go.googlesource.com/proposal/+/refs/heads/master/design/70257-memory-regions.md#annotated-examples https://go.googlesource.com/proposal/+/refs/heads/master/des... I think the deeper issue is that Go's garbage collector is just not performant enough. And at the same time, Go is massively parallel with a shared-everything memory model, so as heaps get bigger, the impact of the imperfect GC becomes more and more noticeable. Java also had this issue, and they spent decades on tuning collectors. Azul even produced custom hardware for it, at one point in time. I don't think Go needs to go in that direction.