> > > > Any particular reason you avoided something like sync.Pool ? It could be useful in your case, allocation pattern depending. > > > Hi, > > I initially evaluated the sync.Pool then I read this article: > > https://dzone.com/articles/memory-pooling-in-go-where-why-and-how > > and this issue: > > https://github.com/golang/go/issues/23199
So If I understand go/issues/23199 correctly, the problem is that large allocations from the past hang around in the pool (and apparently this is made worse by small allocations somehow pinning them). I can see how this can be a problem, but is it a problem *for you*? You say that the allocations in question are for packets -- which I would assume all count as small. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAN%2BHj7hWu7OH%2BhSm8KLX7o8au4Y%2BEpxpSmTYeuLHeQQ%2BMepGhg%40mail.gmail.com.
