I thought so, too. That's why I asked if it would introduce a lot of GC.

The very original version was to allocate outside the loop and reuse it for every iteration. It's fine if the number of receivers is small. But for joining a node with 10 sites to a cluster with 30 partitions, the number of receivers could get up to 300 in the worst case, which is why DBBPool or relying on CompressionService's buffer pool wouldn't help. So I made FixedDBBPool to also pool the decompression buffers so they were bounded.

Should I revert my revert of the FixedDBBPool implementation?