[
https://issues.apache.org/jira/browse/KAFKA-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14383147#comment-14383147
]
Rajiv Kurian commented on KAFKA-2045:
-------------------------------------
Bounding the ByteBuffers and statically allocating them would be great. On
consumers do we need any more than a ByteBuffer per broker that the client is
talking to? Why do we need a buffer per topic/partition? Even if the leader for
a topic/partition changes, we will ultimately know about it and ask the new
leader for data. This data will still be after the previous data for the
topic/partition that moved so to the consumer it will just look like another
message set and order per topic/partition is still maintained.
> Memory Management on the consumer
> ---------------------------------
>
> Key: KAFKA-2045
> URL: https://issues.apache.org/jira/browse/KAFKA-2045
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Guozhang Wang
>
> We need to add the memory management on the new consumer like we did in the
> new producer. This would probably include:
> 1. byte buffer re-usage for fetch response partition data.
> 2. byte buffer re-usage for on-the-fly de-compression.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
