[
https://issues.apache.org/jira/browse/AMQ-7340?focusedWorklogId=776537&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-776537
]
ASF GitHub Bot logged work on AMQ-7340:
---------------------------------------
Author: ASF GitHub Bot
Created on: 31/May/22 20:11
Start Date: 31/May/22 20:11
Worklog Time Spent: 10m
Work Description: lucastetreault commented on PR #728:
URL: https://github.com/apache/activemq/pull/728#issuecomment-1142595809
@lovemai073, I ran some tests again today to make sure everything was
working as I expected. These are against m5.large brokers with EFS storage
running on Amazon MQ.
### 5.16.3 Broker - 100k messages, 100ms delays
It took about 40 seconds to schedule all the message and it seems like it's
able to keep up for a little bit then falls behind and slows down to ~1.9 msg/s
vs. the 10 msg/s that I expect - the change in behaviour a couple of minutes in
could be due to EFS throughput burst balance being exhausted.
```
2022/05/31 12:20:36 Producer - Start: 2022-05-31T12:19:56-07:00, End:
2022-05-31T12:20:36-07:00, Diff: 40.005111s, Count: 100000
2022/05/31 12:20:37 [100] Received message
Issue Time Tracking
-------------------
Worklog Id: (was: 776537)
Time Spent: 2h 20m (was: 2h 10m)
> 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: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 5.16.4, 5.17.0
>
> Attachments: ScheduleActiveMQ.zip
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> 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.7#820007)
