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
Jamie G. <mailto:[email protected]>
27 March 2015 12:37
Thank you for the links - I'll try setting this up on my test lab.

Cheers,
Jamie
Gary Tully <mailto:[email protected]>
27 March 2015 12:29
you can also use the producer/consumer examples from a distro.
Last time I was trying to saturate a network I uses some of the scripts at
https://github.com/gtully/broker-run/blob/master/scripts/clients.sh

I have not been in there for a while but you may find it useful to run
parallel load over multiple destinations.
Jamie G. <mailto:[email protected]>
27 March 2015 10:14
Hi All,

It was mentioned on another thread that ActiveMQ has hard challenges
with CPU core/thread scaling - I was wondering if there was a test
case/script published some where that shows this issue occurring?

Cheers,
Jamie

Reply via email to