[
https://issues.apache.org/jira/browse/AMQ-7340?focusedWorklogId=775793&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-775793
]
ASF GitHub Bot logged work on AMQ-7340:
---------------------------------------
Author: ASF GitHub Bot
Created on: 30/May/22 07:25
Start Date: 30/May/22 07:25
Worklog Time Spent: 10m
Work Description: jbonofre commented on PR #728:
URL: https://github.com/apache/activemq/pull/728#issuecomment-1140797386
@lovemai073 I just double checked and actually, the change is included on
5.16.x:
```
commit fc7a68a8bcf24492d3b2fe5426d366103b3e0e8f
Author: Lucas Tétreault <[email protected]>
Date: Wed Nov 24 01:06:47 2021 -0800
Use B+ Tree iterator instead of DFS to find scheduled jobs to be executed
(cherry picked from commit 60859b0b7fa93b001ca2b0ac2f2385386cb2f47d)
```
So, it's included in ActiveMQ 5.16.4.
Issue Time Tracking
-------------------
Worklog Id: (was: 775793)
Time Spent: 1.5h (was: 1h 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.17.0, 5.16.6
>
> Attachments: ScheduleActiveMQ.zip
>
> Time Spent: 1.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)
