[
https://issues.apache.org/jira/browse/AMQ-7340?focusedWorklogId=775907&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-775907
]
ASF GitHub Bot logged work on AMQ-7340:
---------------------------------------
Author: ASF GitHub Bot
Created on: 30/May/22 13:34
Start Date: 30/May/22 13:34
Worklog Time Spent: 10m
Work Description: lovemai073 commented on PR #728:
URL: https://github.com/apache/activemq/pull/728#issuecomment-1141167833
My test scenario is the same as mentioned by @lucastetreault.
- MQ version: Broker engine version 5.16.4
- Broker instance type:
[mq.m5.large](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/broker-instance-types.html#activemq-broker-instance-types)(vCPU:8
memory:8G) host on AWS MQ service.
- Test case: Test 500ms and 1000ms delayed messages in the 2 different MQ.
- send message volume is 100,000
-message size is a string of consecutive numbers (ex: 000000~099999)
#### 1. 500ms：
Using 100,000 messages, each message delay is accumulated to 500ms. In this
case, the consumer can consume the message in about 500~800ms.
#### [The 30,000th time spent]
----------
[2022-05-25 11:46:46.574] 1
Issue Time Tracking
-------------------
Worklog Id: (was: 775907)
Time Spent: 2h 10m (was: 2h)
> 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 10m
> 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)
