mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeanfrancois Arcand <jfarc...@apache.org>
Subject Re: To keep direct buffer support or not
Date Fri, 08 Dec 2006 20:01:27 GMT
Hi Trustin,

Trustin Lee wrote:
> Hi,
> 
> In the recent discussion (
> http://www.nabble.com/Is-MINA-ByteBuffer-pool-of-dubious-value--tf2652301.html#a7401135),

> 
> we agreed on removing acquire() / release() methods and pooling stuff.  I
> think it's a great idea, but what do we do now with direct buffers?  They
> take longer to allocate / deallocate, and that was why we introduced 
> pooling
> feature.  Are we just abandoning direct buffers and let users manage the
> buffer in their own way?
> 
> A possible alternative could be providing a separate direct buffer manager
> for only those who uses direct buffers, but considering the current
> performance results, we won't need to provide this feature for a long time.
> And eventually, it might not be a duty of MINA but a duty of JVM
> implementation to manage allocated direct buffers effectively.  We might be
> trying to resolve the problem that we are not supposed to resolve.  What do
> you think?

do you know if someone filled a bug against SUN JDK? If people have a 
reproducible unit test, I can escalate it with the NIO team so it gets 
fixed. I'm also seeing the same "problem" with direct bb but just don't 
have the cycle to write a clear test case.

Thanks

-- Jeanfrancois


> 
> Trustin

Mime
View raw message