Hi,<div><br></div><div>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>).</div>
<div><br></div><div>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>).</div>
<div><br></div><div>I am wondering if OrderedMemoryAwareThreadPoolExecutor is needed if the boss and worker thread pools are created with Executors.newCachedThreadPool().</div><div><br></div><div>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?</div>
<div><br></div><div>Thanks.</div><div><br></div><div>Regards</div><div>Vibul</div><div><br></div><div><br><br><div class="gmail_quote">On 22 September 2011 01:32, Norman Maurer <span dir="ltr"><<a href="mailto:norman.maurer@googlemail.com">norman.maurer@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">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>
<div class="im"><br>
Bye,<br>
Norman<br>
<br>
<br>
2011/9/21 men10 <<a href="mailto:menimmailim@yahoo.com">menimmailim@yahoo.com</a>>:<br>
</div><div><div></div><div class="h5">> 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" target="_blank">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" target="_blank">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><br>
<a href="https://lists.jboss.org/mailman/listinfo/netty-users" target="_blank">https://lists.jboss.org/mailman/listinfo/netty-users</a><br>
</div></div></blockquote></div><br></div>