I'm running Artemis 2.14, and one of the systems publishing to it creates a
lot of separate tasks -- from its perspective. I can see on Artemis that
the Total connection count vs Total messages acknowledged is pretty close,
so it's apparent that the client system is making use of the anti-pattern
of creating a new connection for each message it publishes. I don't have
access to the client system implementation, but is there anything I can do
on the Artemis end to make it more efficient? Latency with this system is
becoming an issue. Also every 30 minutes or so there is a spike in CPU
usage (~50%) which I assume is garbage collection. During that spike
message publishing slows down a lot.

Thanks,

Ben

Reply via email to