Why Netty's CompositeByteBuf consolidates automatically if the number of components in CompositeByteBuf exceeds 'maxNumComponents'
Question
I'm trying to understand why CompositeByteBuf, consolidates if the number of components in the compositebytebuf becomes more than 'maxNumComponents' while adding component ?
This consolidation involves copy operations . My questions are -
- why CompositeByteBuf is doing this consolidation automatically if the number of components is greater than 'maxNumComponents'? what is the advantage in doing so?
- Will there be any disadvantage if we explicitly set 'maxNumComponents' to very high number, so that consolidation will not be triggered.
1 answers
solution1
0 2020-11-24 09:02:54
It does this because once you have a lot of buffers in a CompositeByteBuf accessing things on a specific index can for example become very slow.
If this is a problem for you or not depends highly on the use-case.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.
Related Question
Is netty CompositeByteBuf direct or indirect
Accumulating Netty direct IO buffer to CompositeByteBuf
CompositeByteBuf has readableBytes return 0
Micronaut HttpResponse body CompositeByteBuf type throws io.netty.util.IllegalReferenceCountException: refCnt: 0
I wonder if netty's directBytebuf will be automatically recycled
Netty: Weird IndexOutOfBoundsException: readerIndex + length exceeds writerIndex
Netty: Number of outstanding requests
Usage of Netty's ChannelLocal
Netty - number of concurrent client connections
Can Netty automatically handle queueing of requests?
Related Tags