FrameDecoder and cumulation size

[이희승 (Trustin Lee)]

I am aware of this issue and actually was thinking about what the best solution would be. Thank you for sharing your idea. If anyone has other ideas, please let me know.

Thanks 

-- 
Trustin Lee (http://gleamynode.net/)

On Wednesday, August 24, 2011 at 10:24 PM, Thibaut wrote:

> Sometimes we make concurrent larger requests (> 30 MB) through elasticsearch
> and the buffers are still kept afterwards, even though we don't use them
> anymore afterwards. This causes us to have more than 400 MB of allocated
> buffers in our heap which we don't use.
> 
> It would be great if it would be possible to drop the allocated buffers
> after they are not used for a while anymore. Or even reduce the buffer size
> if the last 100 requests were more than of a factor of 2 smaller than the
> largest request.
> 
> 
> 
> 
> --
> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/FrameDecoder-and-cumulation-size-tp6596595p6720135.html
> Sent from the Netty User Group mailing list archive at Nabble.com (http://Nabble.com).
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org (mailto:netty-users at lists.jboss.org)
> https://lists.jboss.org/mailman/listinfo/netty-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-users/attachments/20110825/0672aae0/attachment.html