This was a while ago - but single broker, 20 producers, 20 consumers, 1k messages - different message config - including flow control on/off. Actually thinking about it - would be worth using Hiram's performance tests he put together - see - https://github.com/chirino/jms-benchmark

artnaseef <mailto:[email protected]>
27 March 2015 16:37
A higher load on CPU versus other brokers under the exact same load?

Are there any reports with details, such as the topology of brokers and
ActiveMQ clients?

It would be great to have a baseline to start from, and some detail to
review. For example, not being able to saturate a network connection with a
single client connection to ActiveMQ would not be a surprise.

Things I would be interested to know about these tests:
* Numbers of brokers and broker topology
* Numbers of ActiveMQ producers and consumers, and their topology wrt the
ActiveMQ broker topology
* Types and sizes of messages
* ActiveMQ broker configuration



--
View this message in context: http://activemq.2283324.n4.nabble.com/CPU-core-thread-scaling-test-tp4693913p4693951.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Rob Davies <mailto:[email protected]>
27 March 2015 14:18
I've compared ActiveMQ on the same network/machines against other Java brokers - and ActiveMQ always has a higher load on CPU. My suspicion is around thread context switching in the broker - but a fresh set of eyes is greatly appreciated!

Jamie G. <mailto:[email protected]>
27 March 2015 13:20
Hmm, I'd want to look a bit closer at the network stack -- I've
observed on other projects NICs off loading heavily onto the CPU at
higher push rates (see Freed-up CPU cycles
http://en.wikipedia.org/wiki/TCP_offload_engine).

-Jamie
Hiram Chirino <mailto:[email protected]>
27 March 2015 13:11
What ideally should happen is that under high load the network should
be the bottleneck. But right now CPU is the bottleneck.

On Fri, Mar 27, 2015 at 8:53 AM, James Carman



James Carman <mailto:[email protected]>
27 March 2015 12:53
Is the expected behavior that even under high load AMQ would only be
using one core/CPU, or less than it could/should be in some way?

Reply via email to