activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <>
Subject Re: JMS to STOMP transformation causes throughput drop in STOMP consumers
Date Thu, 07 Apr 2016 05:31:19 GMT
Which process is the one spinning the CPU: the broker, or your client?

If it's the broker, you're in luck: the ActiveMQ broker is a Java process,
which means that all of the standard Java profiling tools (which will tell
you where a Java application is spending its time) are at your disposal and
can tell you why serialization is slow.  JVisualVM's profiler would
probably give you a pretty good starting point for answering your question,
and it's deployed as part of the JVM so you don't even have to install any
special tools...


On Wed, Apr 6, 2016 at 2:17 AM, xabhi <> wrote:

> Hi,
> I am seeing the same behavior with Python STOMP consumer as well -
> throughput for TEXT msgs is 10K/s and for MAP messages with tranformation
> is
> 200 msgs/s.
>  Is there a way to improve it for JMS Map messages? Some broker setting?
> may
> be plugin different serialization library instead of xstream?
> Thanks,
> Abhishek
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message