Unfortunately I can't lower that processing time, application is supposed to authorize credit card transactions, and to do that it needs to make remote calls to a credit card authorizer system and that's taking around 1000 ms on average. So I guess I will give the new settings a try tonight, and will write a small test application to test that.
Erinc On Mon, Mar 29, 2010 at 6:31 PM, Emmanuel Lécharny <[email protected]>wrote: > On 3/30/10 12:24 AM, Erinc Arikan wrote: > >> Thanks for the great explanation, so If I have 2 dual core >> processors,(number of processors + 1) IOProcessors which is 5 IoProcessors >> in my case. >> >> Only way I can configure number of IOProcessors is as follows: So I can >> either use: >> >> SimpleIoProcessorPool pool = new >> SimpleIoProcessorPool<NioSession>(NioProcessor.class,5); >> final IoAcceptor acceptor = new NioSocketAcceptor(pool); >> >> or >> >> final IoAcceptor acceptor = new NioSocketAcceptor(5); >> >> but I guess since I have only one IoAcceptor in my server class, I >> shouldn't >> use SimpleIoProcessorPool at all and I should go with: >> >> final IoAcceptor acceptor = new NioSocketAcceptor(5); >> >> So this means that I will have 5 IoProcessors for a single IoAcceptor, so >> hopefully that will give me some performance increase. >> >> On top of this if I have an executorfilter with 40 threads, I feel like I >> can deal with 40 requests per second. >> >> Because each IoProcessor will have 8 requests queued up which individually >> takes 1 second to complete unless there's a race condition somewhere, it >> should be possible to process 40 requests per second, am I wrong? >> >> > Sounds a correct assumptin, but has to be tested. > > Can't you lower the time it takes to process a request ? 1 seconds is like > 1000 years for a computer ... > > > -- > Regards, > Cordialement, > Emmanuel Lécharny > www.nextury.com > > >
