Good news, Emmanuel!
I believe that any project has its own problems (not visible from the
first sight!) - mina, netty, grizzly... Maybe in different situations ;)
I will stay with mina and will try to help to debug and speed up it
wherever possible. For now, our servers do not require high throughput,
it is not critical for us. But we are trying to handle more client
sessions per server, so one day the throughput will be important for me too!
As for architecture - yes, we should clarify and improve it in mina 3.0,
but now it's time to finalize mina 2.0 - this version should be reliable
enough and fast. After that we can think about additional config params,
I/O throttling, etc - maybe in 2.5 ? ;)
I am thinking about how we could call 3.0 - maybe, Mina 3.0 "Reloaded"? ;)
Victor N
Emmanuel Lecharny wrote:
Hi guys,
today, I spent some time debugging MINA, and doing some perf tests
(minimal ones). I was chasing a bug in the way messages are written back
to client. It appeared that in order to send the messageSent event, we
had to reset the buffer we just sent (otheriwse the filters have no way
to get the content of this buffer). The problem is that the buffer
remained reset, and MINA thought that it should be processed again (but
not send again, hopefully). By repositionning the buffer to its previous
position, I was able to speed up the server by 5%.
Not too bad... I'm sure there are many areas where we can improve the
server. let's do that whne 2.0 will have been released !
