I'm not sure I understood your question, but adding an ExecutorFilter is only effective when the cost of handling events outweighs the cost of adding a thread pool. For example, echo server's biz logic is very trivial so it simply doesn't need an ExecutorFilter. Because calling Executor.execute() and letting other threads than I/O processor threads handle the event takes much more time.
On Thu, 2008-03-27 at 18:26 +0900, ryan cheng wrote:
> now I remove the ExecutorFilter, just using the echoserver demo code :
>
> chain.addLast("threadPool", new ExecutorFilter(threadPool)); // remove
> this code
>
> Using JMeter test again,
> the JMeter parameters is same:
> Thread Num: 600
> Ramp-up Period(in Seconds):1
> loop num: 1
>
> the samper: tcp samper
> timeout:5000
> no dely: ture
>
> now I find the 600 thread is all right.
> after add ExecutorFilter ,I got some thread is wrong.
> I thought the ExecutorFilter was used for improving the performance, where I
> am wrong?
>
> thanks.
--
Trustin Lee - Principal Software Engineer, JBoss, Red Hat
--
what we call human nature is actually human habit
--
http://gleamynode.net/
signature.asc
Description: This is a digitally signed message part
