Re: [PR] Fix Direct Memory OOM on Server [pinot]

["gortiz (via GitHub)" <gi...@apache.org>]

gortiz commented on PR #15335:
URL: https://github.com/apache/pinot/pull/15335#issuecomment-2771487196

   Idea: instead (or maybe complementary) of trying to free Netty's memory when we are getting out of it... could we try to limit the amount of memory being used by Netty? By default Netty's pools consume 2/3 of the offheap memory, which is fine for normal apps that don't use offheap memory theirself but probably is too much for us. This can be tuned by system properties but also using allocators with explicit memory limits. See https://github.com/netty/netty/blob/a785e5b3d1e11a40fa61757c7a119333ad459c20/buffer/src/main/java/io/netty/buffer/PooledByteBufAllocator.java#L69


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org