Lari Hotari

> This update adds support for unpooled memory allocation off-heap, allowing greater flexibility in memory management and reducing GC pressure in certain workloads. how does this reduce GC pressure in...

This is a problem with #268 since the installation succeeds with `--version 0.6.2`.

that seems like a strange flamegraph. I don't see how readBytes could trigger CRC calculation. ByteBufVisitor is used in checksum calculations: https://github.com/apache/bookkeeper/blob/f8eb7a06a683e690e8a70b5bd72927e4df70aa51/bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/checksum/DigestManager.java#L69-L71 PR was #4196

> The ByteBuf was not coming from a read from the BookKeeper client, because the ByteBug is coming from the network (it is the Pulsar producer that is sending a...

> I also found the checksum cost a lot of CPU @hangc0276 I guess it is expected to consume a lot of CPU? In Enrico's case, the flamegraph doesn't seem...

> 1. When message size is large with high filtering ratio, due to Pulsar's default configuration of `dispatcherMaxReadSizeBytes=5MB` and `dispatcherMaxBatchSize=100`, a single `readMoreEntries()` batch can easily reach the maximum read...

There a blog post by AutoMQ folks about PooledByteBufAllocator memory fragmentation: https://www.automq.com/blog/netty-based-streaming-systems-memory-fragmentation-and-oom-issues . I guess the blog post was written before [AdaptiveByteBufAllocator](https://netty.io/4.1/api/io/netty/buffer/AdaptiveByteBufAllocator.html) became usable. It would be interesting to also...

> Broker Operating system and hardware type: 5.4.241-1-tlinux4 (cloud vendor host Linux distributions, acted like CentOS) Since this is glibc based, have you considered tuning glibc parameters? #24692 mentions some...

@cccdemon Sounds like a useful improvement. Would you like to contribute a pull request? This Helm chart is community maintained so pull requests are preferred so that we can improve...

@cccdemon There's #523 with a related change. That has been merged.