[
https://issues.apache.org/jira/browse/AMQ-7340?focusedWorklogId=777988&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-777988
]
ASF GitHub Bot logged work on AMQ-7340:
---------------------------------------
Author: ASF GitHub Bot
Created on: 03/Jun/22 09:09
Start Date: 03/Jun/22 09:09
Worklog Time Spent: 10m
Work Description: lovemai073 commented on PR #728:
URL: https://github.com/apache/activemq/pull/728#issuecomment-1145761690
Hi @lucastetreault,
Thanks for the tip, I noticed that I was missing a main test case.
I did the following test again with the new MQ environment.
- MQ version: Broker engine version 5.16.4
- Broker instance type: mq.m5.large(vCPU:8 memory:8G) with EBS host on AWS
MQ service.
- Test case: Test 100ms delayed messages. This is the main issue in the
previous version.
- send message volume is 100,000 via 1 producer
- message size is a string of consecutive numbers (ex: 000000~099999)
- consumer: Use 4 consumers, I noticed that delay time is 100ms, which means
that the consumer must get 10+ messages in 1 second.
#### Test-1. 100ms with 4 consumer.
The expected time for the message to be consumed
>((100000*100)/1000) / 60 = 166.67mins
166.67 / 60 = 2.7H
Actual consumption time
>StartTime: 2022-06-02 14:50:13.276
EndTime:2022-06-02 17:37:39.99
Total: 2H 48Mins => 168 mins
#### Test-2. 100ms with 4 consumer.
The expected time for the message to be consumed
>((100000*100)/1000) / 60 = 166.67mins
166.67 / 60 = 2.7H
Actual consumption time
>StartTime: 2022-06-03 04:04:45.827
EndTime:2022-06-03 06:53:35.489
Total: 2H 48Mins 49sec => 168 mins
### Summary
From the above test results, I can be confirmed that the issue has been
fixed and the process performance has been improved in the new version.
Thanks for your help, let me notice the missed test case.
Issue Time Tracking
-------------------
Worklog Id: (was: 777988)
Time Spent: 2.5h (was: 2h 20m)
> 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: 2.5h
> 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)
