On Thu, 27 Sep 2018, at 3:06 PM, Peter Mogensen wrote: > > > On 09/27/2018 03:58 PM, Robert Engels wrote: > > It wasn’t necessarily a warning to you :) > > > > It comes from the days of GC bashing in Java and so everyone tried to > > manually write garbage free programs using pools and it had a bad effect on > > both performance and reliability. GC is there for a reason, use it... :) I > > would just hate to see Go developers “go” down the same path... > > Well... being blissfully ignorant of JVM garbage collection pain.... I > occasionally use sync.Pool to improve code in Go with measurable > results. I've never really found it difficult to know when to call Put() >
https://github.com/golang/go/issues/23199 describes another gotcha when using pools: pinning of memory buffers. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
