Hi there,<br><br>I dont found any performance issues with OrderedMemoryAwareThreadPoolExecutor yet so I would use it...<br><br>And if you have blocking code you will need it as even if you use a CachedThreadPool. This is because the numer of IOWorker is fixed.<br>
The default is 2 x num cpu.<br><br>bye<br>norman<br><br>Am Freitag, 23. September 2011 schrieb Vibul Imtarnasan <<a href="mailto:vibuli@gmail.com">vibuli@gmail.com</a>>:<br>> Hi,<br>> I've read that the OrderedMemoryAwareThreadPoolExecutor has performance issues (<a href="http://web.archiveorange.com/archive/v/ZVMdIF9d6poqpmuvDOuq">http://web.archiveorange.com/archive/v/ZVMdIF9d6poqpmuvDOuq</a>).<br>
> Also, it did not work for me on my HTTP server when used with compression (<a href="http://www.jboss.org/netty/community#nabble-td6303816">http://www.jboss.org/netty/community#nabble-td6303816</a>).<br>> I am wondering if OrderedMemoryAwareThreadPoolExecutor is needed if the boss and worker thread pools are created with Executors.newCachedThreadPool().<br>
> From my reading of the documentation on CachedThreadPool, new threads are created as needed. Hence, if a database read blocks, wont a new thread be used to handle new incoming requests?<br>> Thanks.<br>> Regards<br>
> Vibul<br>><br>><br>> On 22 September 2011 01:32, Norman Maurer <<a href="mailto:norman.maurer@googlemail.com">norman.maurer@googlemail.com</a>> wrote:<br>>><br>>> You still need your own handler. The ExecutionHandler just take care<br>
>> to "execute" your handler in a new thread (outside of the io-workers).<br>>><br>>> Bye,<br>>> Norman<br>>><br>>><br>>> 2011/9/21 men10 <<a href="mailto:menimmailim@yahoo.com">menimmailim@yahoo.com</a>>:<br>
>> > Thank you for reply<br>>> ><br>>> > So I guess I should execute querys in Execution<br>>> > Handler(OrderedMemoryAwareThreadPoolExecutor) and if create pool in<br>>> > executionhandler (is it a good idea?) I dont need any other handler right?<br>
>> ><br>>> ><br>>> ><br>>> > Norman Maurer-2 wrote:<br>>> >><br>>> >> You should add an ExecutionHandler in front of your handler otherwise<br>>> >> you will block the worker thread.<br>
>> >><br>>> >> Bye,<br>>> >> Norman<br>>> >><br>>> >><br>>> ><br>>> ><br>>> > --<br>>> > View this message in context: <a href="http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Netty-with-DB-tp6815567p6816444.html">http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Netty-with-DB-tp6815567p6816444.html</a><br>
>> > Sent from the Netty User Group mailing list archive at Nabble.com.<br>>> > _______________________________________________<br>>> > netty-users mailing list<br>>> > <a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a><br>
>> > <a href="https://lists.jboss.org/mailman/listinfo/netty-users">https://lists.jboss.org/mailman/listinfo/netty-users</a><br>>> ><br>>> _______________________________________________<br>>> netty-users mailing list<br>
>> <a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a> <<a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a>><br>>> <a href="https://lists.jboss.org/mailman/listinfo/netty-users">https://lists.jboss.org/mailman/listinfo/netty-users</a> <<a href="https://lists.jboss.org/mailman/listinfo/netty-users">https://lists.jboss.org/mailman/listinfo/netty-users</a>><br>
><br>>