You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by GitBox <gi...@apache.org> on 2021/08/28 00:53:30 UTC

[GitHub] [kafka] tusharg1993 commented on pull request #11204: KAFKA-13188 - Release the memory back into MemoryPool

tusharg1993 commented on pull request #11204:
URL: https://github.com/apache/kafka/pull/11204#issuecomment-907540893


   @aloknnikhil Hey, Tushar here. I am the original author for the PR. Thanks for forward porting the change apache/kafka trunk. 
   
   Some background. This change is essentially a very nice improvement that we saw especially when KafkaConsumer is lagging and try to fetch as much as data possible from brokers. 
   
   This becomes a GC problem because this long withstanding allocation of memory can promote to old gen in cases where we are lagging. The solution to this is to pool these buffers inside kafka library such that only first few instances are allocated and then the network code tries to reuse them in order to relieve the memory pressure in terms of new allocations per sec and amount of data that gets promoted to OldGen


-- 
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: jira-unsubscribe@kafka.apache.org

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