2 ms·
Yeah I thought sync.Pool might be involved. But I don't see how this would negatively impact the GC, since using a pool almost always reduces the amount of garb
by infogulch 11y ago
Yeah I thought sync.Pool might be involved. But I don't see how this would negatively impact the GC, since using a pool almost always reduces the amount of garbage.
- pxue 11y agoUnlike in C you can't tell the garbage collector to "ignore" a large chunk of the memory allocated in the buffer. what ends up happening is Go's GC spends lots of time traversing the heap and marking anyway and end up doing nothing. I know they've made optimizations like here https://github.com/golang/go/issues/9477 https://github.com/golang/go/issues/9477 but I haven't followed it up and gave it another look yet.