Re: sharing Executor between IoServices

[Cem Uzunlar <ce...@gmail.com>]

Hi,

1) ExecutorService es = new OrderedThreadPoolExecutor();

is this a correct thread pool for using as a global thread pool? (For
IoServices and ExecutorFilters)

2) NioSocketAcceptor acceptor = new NioSocketAcceptor(es, XXX);

What must i write as the second parameter XXX ? (processor)

3) What is the best core and maximum thread count for the
OrderedThreadPoolExecutor? (For a board game server application)

2 * Runtime.getRuntime().availableProcessors() + 1 for "IoServices +
ExecuterFilters"

is that ok?

Thanks...

--
Cem Uzunlar

2007/10/5, Trustin Lee <tr...@gmail.com>:
>
> On 10/4/07, Mark <el...@gmail.com> wrote:
> > In the Confuguring Thread Model tutorial (
> > http://mina.apache.org/configuring-thread-model.html), is says
> >
> > "It is not recommended to share one thread pool for IoServices and
> > ExecutorFilters."
> >
> > Is it OK to use the same executor that gets passed in to a
> > NioSocketAcceptor's constructor?  I think that this could help solve the
> > issue I entered into JIRA (
> https://issues.apache.org/jira/browse/DIRMINA-453
> > )
>
>
> It is OK as long as:
>
> * cached thread pool is used or
> * you counted the number of required thread correctly. :D
>
> With global worker thread pool, things will become much easier as you
> said.
>
> Trustin
> --
> what we call human nature is actually human habit
> --
> http://gleamynode.net/
>
> --
> PGP Key ID: 0x0255ECA6
>