3 ms·
I'm curious about this. Go has a history of doing the simplest thing that covers the majority of cases, inherited from Plan 9. For one thing, although I don't
by mcguire 9y ago
I'm curious about this.
Go has a history of doing the simplest thing that covers the majority of cases, inherited from Plan 9. For one thing, although I don't know its current GC story, its original collector was very simple.
I wonder what would happen if you transplanted a recent collector from Java, where the strategy is to optimize the crap out of anything that moves, into Go?
Obviously, it wouldn't be as fast as not allocating, or at least not collecting, in hot code, but what would be the actual penalty?
On the other hand, what about, say, Pony and its per-thread collectors?
- stmw 9y agoFrom a recent talk on the latest JDK GC, it seems to require even more tuning parameters than before. So the best performance achievable may be higher, but with more manual work. Which is along the same trade-off curve, with malloc/free on one end, and a very simple GC on the other.