Sane Number of Threads

["이희승 (Trustin Lee)"]

The default should work fine but it's a better idea to run the test with
different worker counts to get the optimal performance.

If you increase the I/O thread worker count, you might not need to add
ExecutionHandler assuming the business logic does not block too long.
Of course, the definition of 'too long' depends on how much latency you
can accept. :-)

On 05/19/2011 04:34 PM, Marc-André Laverdière wrote:
> I think that the rule of thumb they said is twice the number of cores.
> Of course, your worker thread pool in the execution handler can be much bigger.
> 
> On 5/19/11, Dustin Norlander <dustinn at gmail.com> wrote:
>> Wondering how big to make the I/O threadpool.  I am currently using an
>> Execution handler so my code should all be executed in a separate
>> thread, just wondering how many threads to assign to the IO pool?
>>
>> Seems with asynch i/o the number of io threads should be very small
>> since it should not ever block, is this correct?  any reason to ever
>> assign more threads then the # of cores?
>>
>> thanks for any advice,
>> Dustin
>> _______________________________________________
>> netty-users mailing list
>> netty-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/netty-users
>>
> 
> 


-- 
Trustin Lee, http://gleamynode.net/