TimeoutHandlers consume too many resources (bug)

[Dave Siracusa]

I integrated timeout handlers in my server.  I exercise my server via jmeter
using 10 threads, 10 iterations.  After several runs, I noticed that the
server responsiveness goes way down from 6KB/sec to <1kB/sec.

I inspected the java process in Windows 2003 Server taskmanager and found
the handle count in excess of 16k, memory at 120MB, CPU utilization > 90%
even after my tests were completed.  I brought down process explorer from
sysinternals.com and inspected the native java process and noticed thousands
of native windows threads.  
I receive no timeout exceptions during the tests.

I repeated the tests with the ReadTimeoutHandler and WriteTimeoutHandler
commented out and the thread count is 100-125, memory is 25MB, and CPU at 0%
minutes after the test.
The performance is faster than the with the handlers and stays consistent
from run to run.



-- 
View this message in context: http://n2.nabble.com/TimeoutHandlers-consume-too-many-resources-%28bug%29-tp2298966p2298966.html
Sent from the Netty User Group mailing list archive at Nabble.com.