Probably you could increase the backlog of the acceptor? You will also have to redesign your protocol so a client makes a connection only once and reuse it on and on, instead of opening and closing connections frequently.
On Fri, 2008-03-28 at 11:39 +0900, ryan cheng wrote: > Hi ,Trustin > thanks for the reply. now I understand when using ExecutorFilter. > > but,my question is, when the acceptor is bind and starting to accept > incoming connections, how to open a lots of IoSessions to handle the > incoming connections. also you can say, I want build a IoSession pool (like > database connection pool), and put these IoSessions to open and wate > incoming connections. I wish through this way can improve the throughput. > but I donot know is this a right way? > > maybe you can get me a clue. > > 2008/3/28, 이희승 (Trustin Lee) <[EMAIL PROTECTED]>: > > > > I'm not sure I understood your question, but adding an ExecutorFilter is > > only effective when the cost of handling events outweighs the cost of > > adding a thread pool. For example, echo server's biz logic is very > > trivial so it simply doesn't need an ExecutorFilter. Because calling > > Executor.execute() and letting other threads than I/O processor threads > > handle the event takes much more time. > > > > -- Trustin Lee - Principal Software Engineer, JBoss, Red Hat -- what we call human nature is actually human habit -- http://gleamynode.net/
signature.asc
Description: This is a digitally signed message part
