>
> Are we currently underestimating the size of AMQP messages? If so,
> what exactly was underestimated?


If you sent a Core message with ./artemis producer --message-count=1
--protocol=AMQP

The address size of that message will be 642 bytes (from the estimate)

If you send a Core Message with ./artemis producer --message-count=1
--protocol=CORE

The estimate from CORE is using 1121


I believe we need to raise the offset on the AMQP message, raising the minimal.

By pegging I mean.. the broker's performance starts to crawl, using a
lot of time on GC.. and it may eventually OME. It eventually starts to
Page but at that point things are really bad already.



There's another change I have beeen wanting to do, that is to keep the
estimate static... and I want to do it as part of 2.54.0 as I'm not
holding 2.53 for this.


>
> When you say "pegging" are you talking about CPU utilization? If so,
> what is consuming all the CPU? Garbage collection?
>
> If folks potentially need to adjust their paging config we'll need to
> guide them on how to do it in the docs.
>
>
> Justin
>
> On Mon, Mar 16, 2026 at 2:13 PM Clebert Suconic
> <[email protected]> wrote:
> >
> > As I was "playing" with my changes on Shell, I stumbled on an issue.
> >
> >
> > As I sent millions of messages, Core Messages will trigger paging a lot 
> > sooner.
> > While AMQP Messages will trigger it much later, but the broker starts
> > pegging and decreases the performance quite a lot.
> >
> >
> > I played with some adjusting on the estimates, and I will fix it on
> > the next release (2.54.. not 2.53)..
> >
> > Users will have to readjust their estimates though...
> >
> > What do you think?
> >
> > --
> > Clebert Suconic
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>


-- 
Clebert Suconic

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to