[ http://issues.apache.org/jira/browse/DIRMINA-176?page=comments#action_12367819 ]
Michael Link commented on DIRMINA-176: -------------------------------------- I like the idea of partitioning the pool. Each range could have it's own pooling characteristics i. e. longer eviction time for smaller buffers while larger buffers are released sooner. I've worked with the Commons-Pool-Package of Jakarta and found the GenericObjectPool and its configuration quite intuitive to use. Maybe some inspiration can be borrowed from there :-) http://jakarta.apache.org/commons/pool/apidocs/org/apache/commons/pool/impl/GenericObjectPool.html > ByteBuffer pool manager which prevents endlessly increasing pool size. > ---------------------------------------------------------------------- > > Key: DIRMINA-176 > URL: http://issues.apache.org/jira/browse/DIRMINA-176 > Project: Directory MINA > Type: New Feature > Reporter: Trustin Lee > Fix For: 0.9.3 > > The current implementation of ByteBuffer pool is designed to increase its > size for ever; it doesn't decrease at all. This is often a cause of > OutOfMemoryError and unexpedly huge heap size. There's one viable solution > for this issue: > * Remove the buffers which have been unused for a long time from the pool. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
