Hi Ceposta,
When I connect my clients using NIO transport I can see NIO worker threads
in my logs.
Like:
40 5 3 3 0 0 ActiveMQ
InactivityMonitor WriteCheckTimer
41 5 25 25 10 10 ActiveMQ
BrokerService[amqDevBroker] Task-3
42 5 52 52 40 40 ActiveMQ NIO
Worker 3
43 5 22 22 10 10 ActiveMQ
BrokerService[amqDevBroker] Task-4
44 5 21 21 20 20 ActiveMQ
BrokerService[amqDevBroker] Task-6
45 5 21 21 10 10 ActiveMQ
BrokerService[amqDevBroker] Task-5
46 5 29 29 20 20 ActiveMQ NIO
Worker 4
47 5 18 18 10 10 ActiveMQ NIO
Worker 5
48 5 3 3 0 0 ActiveMQ
InactivityMonitor Worker
49 5 16 16 10 10 ActiveMQ NIO
Worker 6
60 5 71 33 50 20 ActiveMQ NIO
Worker 5
62 5 51 27 40 20 ActiveMQ
BrokerService[amqDevBroker] Task-8
63 5 49 31 40 30 ActiveMQ NIO
Worker 6
64 5 43 29 30 30 ActiveMQ
BrokerService[amqDevBroker] Task-9
65 5 34 18 20 10 ActiveMQ
BrokerService[amqDevBroker] Task-10
67 5 36 30 20 20 ActiveMQ NIO
Worker 8
68 5 26 19 10 10 ActiveMQ
BrokerService[amqDevBroker] Task-11
69 5 24 20 10 10 ActiveMQ
BrokerService[amqDevBroker] Task-12
70 5 23 23 10 10 ActiveMQ NIO
Worker 9
71 5 11 11 0 0 ActiveMQ NIO
Worker 10
72 5 1 1 0 0 ActiveMQ NIO
Worker 11
NIO worker threads are increasing as soon as I connects a client. Even if I
am using large number(20) of connections I cannot see any thread reduction
compare to TCP. These threads are continuously increasing with client, which
should not happen in case of NIO.
So I want to know that saturation value, after which number of NIO threads
become constant.
Thanks,
John
--
View this message in context:
http://activemq.2283324.n4.nabble.com/NIO-transport-performance-for-ActiveMQ-tp4670977p4671796.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
