How does MINA handle write throttling? If a server is being developed to handle thousands of concurrent connections then some of the clients will be slow and have their data output buffers getting backed up. Is this still an issue for MINA, or do you handle partial writes and reads along with queueing future requests until space clears on a connections buffer?
Currently I am using an NIO server which has a WritableByteChannel between the socket and my classes handling output. I tried to pump data in different sizes while having anywhere from 100-500 clients. Even with DirectBuffering off when creating my channels I am still getting Direct Buffer out of memory errors because the WritableByteChannel seems to create a temporary direct buffer to handle the overflow, which eventually becomes too large if I have too many clients or too much data hitting the server. But if this is a problem MINA has fixed it would make sense to switch to that. Are there any performance statistics showing if MINA outperforms a regular NIO implementation, or at least comes close? Thanks for any information. I appreciate it. -Jason This e-mail and any files transmitted with it may be proprietary and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the sender. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of ITT Corporation. The recipient should check this e-mail and any attachments for the presence of viruses. ITT accepts no liability for any damage caused by any virus transmitted by this e-mail.
