2009/12/4 rama <rama.rama_at_tiscali.it>
> Hi Alexey,
>
> ok, in that way i am able to run and test my code on winzoz :)
>
> but, a small side effect imho is created using statsthreadpool..
>
> in the past i have open a few ticket asking that the threadpool neet to
> obey
> min/max threadN workers.
>
> for that reason 2 new threadpools was proposed (probably by gustav and
> later patched by others, i didn't remember well sorry)
>
> this 2 threadpools was fixedtp and defaulttp.
>
> By default, selectorthread what kind of threadpool use on the version that
> i have try? (1.9.18-x)
>
> That's because i think that if i change the threadpool i'll lose the mighty
> stuff of having the ability to set max-min
> threadworker number (andall the threads will be spawned and stay there
> forever)
>
> am i in right?
>
>
> Also, will be nice to know something about that :)
> What are the plans for the future (in the default GWS http config)?
> Use a threadpool that obey to min/max, use the "old" fixed size threadpool?
>
>
>
> tnx and sorry for the delay of the mails
>
>
> In what way min max mighty stuff ?.
its costly stuff, it costs concurrency.
Peoples "need" for such things is based on what ?, it severely limits the
throughput of many threads and short jobs.
>
> > Hi Rama,
> >
> > ok, pls. remove all output related "ADD" code, but keep:
> >
> > ExtendedThreadPool threadPool = new StatsThreadPool("MyPool", 3, 5, -1,
> 30l, TimeUnit.SECONDS);
> > gws.getSelectorThread().setThreadPool(threadPool);
> >
> > Probably the issue is in default thread pool configuration.
> >
> > Thank you.
> >
> > WBR,
> > Alexey.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>
>
--
regards
gustav trede