Hi

[Norman Maurer]

Hi there,

I dont found any performance issues with
OrderedMemoryAwareThreadPoolExecutor yet so I would use it...

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.
The default is 2 x num cpu.

bye
norman

Am Freitag, 23. September 2011 schrieb Vibul Imtarnasan <vibuli at gmail.com>:
> Hi,
> I've read that the OrderedMemoryAwareThreadPoolExecutor has performance
issues (http://web.archiveorange.com/archive/v/ZVMdIF9d6poqpmuvDOuq).
> Also, it did not work for me on my HTTP server when used with compression
(http://www.jboss.org/netty/community#nabble-td6303816).
> I am wondering if OrderedMemoryAwareThreadPoolExecutor  is needed if  the
boss and worker thread pools are created with
Executors.newCachedThreadPool().
> 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?
> Thanks.
> Regards
> Vibul
>
>
> On 22 September 2011 01:32, Norman Maurer <norman.maurer at googlemail.com>
wrote:
>>
>> You still need your own handler. The ExecutionHandler just take care
>> to "execute" your handler in a new thread (outside of the io-workers).
>>
>> Bye,
>> Norman
>>
>>
>> 2011/9/21 men10 <menimmailim at yahoo.com>:
>> > Thank you for reply
>> >
>> > So I guess I should execute querys in Execution
>> > Handler(OrderedMemoryAwareThreadPoolExecutor) and if create pool in
>> > executionhandler (is it a good idea?) I dont need any other handler
right?
>> >
>> >
>> >
>> > Norman Maurer-2 wrote:
>> >>
>> >> You should add an ExecutionHandler in front of your handler otherwise
>> >> you will block the worker thread.
>> >>
>> >> Bye,
>> >> Norman
>> >>
>> >>
>> >
>> >
>> > --
>> > View this message in context:
http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Netty-with-DB-tp6815567p6816444.html
>> > Sent from the Netty User Group mailing list archive at Nabble.com.
>> > _______________________________________________
>> > netty-users mailing list
>> > netty-users at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/netty-users
>> >
>> _______________________________________________
>> netty-users mailing list
>> netty-users at lists.jboss.org <netty-users at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/netty-users <
https://lists.jboss.org/mailman/listinfo/netty-users>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-users/attachments/20110923/20f27e9b/attachment.html