[
https://issues.apache.org/jira/browse/AMQ-7340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17448830#comment-17448830
]
Charlie Chen commented on AMQ-7340:
-----------------------------------
[^ScheduleActiveMQ.zip]
Hi, we are also having this issue. In Active MQ version 5.16.3, when broker
attribute schedulerSupport is set to true and put around 3000 messages to
scheduled, the speed of message move from scheduled to queue reduced. I've
tried on m5.large EC2 instance (2 vCPU, 8 GB memory) and locally on my Mac
book, the issue exists.
I've attached an example in C# client. In this example, I create 20 producer
thread sending schedule message with 10s delay, after running for a while, we
can see messages in scheduled page not moving to queue even the 'next scheduled
time' has passed. We have a solution to fix this, will submit PR shortly.
> Scheduled messages performance degrade
> --------------------------------------
>
> Key: AMQ-7340
> URL: https://issues.apache.org/jira/browse/AMQ-7340
> Project: ActiveMQ
> Issue Type: Bug
> Environment: ActiveMQ broker has been started in a docker container,
> with (most likely) sufficient allocation of resources.
> Reporter: Daynews
> Assignee: Matt Pavlovich
> Priority: Minor
> Attachments: ScheduleActiveMQ.zip
>
>
> I have sent lot of scheduled messages with 10ms delay between each to see if
> the broker can cope with high load of scheduled messages. Sending delayed
> messages to the queue works fine, however I get a problem when those messages
> need to be put to the main queue when next schedule time is reached. The rate
> of putting scheduled messages to the main queue drops drastically at around
> 1500-3000 messages. I tried to search for a potential cause why this happen,
> but was not able to indicate anything. Even restarting the broker or cleaning
> the main queue, the rate of putting scheduled messages stays at ~0.5s leaving
> many scheduled messages behind.
> Does anyone know a potential cause for his problem? Is this performance
> bottleneck or insufficient resources or badly configured RabitMQ (I've used
> default settings).
> Thanks for the support.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
