There's lots of ways to deal with this kind of situation, e.g.: - Add more (or faster) consumers to keep the backlog of messages lower - Start paging sooner - Configure a limit for paging [1] - Increase the heap size - Implement clustering or federation to scale horizontally
It's hard to provide specific recommendations since use-cases can vary so much. Justin [1] https://activemq.apache.org/components/artemis/documentation/latest/paging.html#configuration-2 On Tue, Apr 30, 2024 at 9:29 AM William Crowell <wcrow...@perforce.com.invalid> wrote: > Justin, > > Thanks. I have the max heap (-Xmx) set at 5GB and the global-max-size set > to 1GB, and I am finding this is not enough for the amount of messages > being put on the broker. This is on an m6g.large AWS instance which has 2 > CPUs and 8GBs of memory. Maybe should I consider a larger instance size or > horizontally scaling? > > Regards, > > William Crowell > > From: Justin Bertram <jbert...@apache.org> > Date: Tuesday, April 30, 2024 at 10:13 AM > To: users@activemq.apache.org <users@activemq.apache.org> > Subject: Re: org.apache.activemq.artemis.core.server.impl.QueueImpl > Instances > There should just be one instance of QueueImpl per queue. Keep in mind that > any JMS topic subscription will be represented as a queue. > > > Justin > > On Tue, Apr 30, 2024 at 8:46 AM William Crowell > <wcrow...@perforce.com.invalid> wrote: > > > Good morning, > > > > I was analyzing a heap dump for Apache Artemis and noticed a high amount > > of org.apache.activemq.artemis.core.server.impl.QueueImpl instances. > There > > were 894 of these instances along with 894 instances of > > org.apache.activemq.artemis.core.paging.cursor.impl.PageSubscriptionImpl. > > > > Does this mean there are 894 different queues defined or are multiple > > instances of QueueImpl created per queue? > > > > Regards, > > > > William Crowell > > > > > > This e-mail may contain information that is privileged or confidential. > If > > you are not the intended recipient, please delete the e-mail and any > > attachments and notify us immediately. > > > > > > > CAUTION: This email originated from outside of the organization. Do not > click on links or open attachments unless you recognize the sender and know > the content is safe. > > > This e-mail may contain information that is privileged or confidential. If > you are not the intended recipient, please delete the e-mail and any > attachments and notify us immediately. > >
