Github user michaelandrepearce commented on the issue: https://github.com/apache/activemq-artemis/pull/1793 @RaiSaurabh @franz1981 I just got some perf results back on this, and its not pretty. (i retract my prev comments (i deleted) After looking again it seems like all this is, is a clone of the CoreMessage, and still on send / inbound, its being converted from 5.x Message to this, instead of taking the underlying, as such its adding more overhead. The intent of a native Message type, is that it holds the protocol specific objects internally as much as possible an operates/delegates to them, meaning that if on consume there was no changes or anything the same protocol specific object can be fired back out.
---