Hi @hachikuji we've updated the way responses are deallocated. Based on the schema, we know which ones contain fields backed by a ByteBuffer and need to be deallocated after a full data consumption. The FetchResponse is a special case as its buffer gets sliced into many CompletedFetches.
We've added a test that uses the `GarbageCollectedMemoryPool` (which we plug into the factory) to check for failed deallocations and reads after deallocation. We'll post later some data about the memory usage of a Consumer with and without a MemoryPool. Feedback welcome :-) [ Full content available at: https://github.com/apache/kafka/pull/4934 ] This message was relayed via gitbox.apache.org for [email protected]
