AdaptiveRecvByteBufAllocator seems to only adjust its buffer size when readComplete() is called. However, readComplete() is not called until it ran out of the data to read. Therefore, the buffer size will not be adjusted until it ran out of the data to read. I find that this logic is a little twisted. The buffer size should keep increasing until it could read the entire set of data in one batch (or reach the maximum buffer size limit), isn't it? Currently, the logic seems to rely on continueReading() logic to read at least 16 messages before stopping to ensure that the buffer size will be eventually increased.
-- You received this message because you are subscribed to the Google Groups "Netty discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/netty/171f78b9-0a6a-423d-9189-575a31a48755%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
