[jira] [Work logged] (AMQ-7340) Scheduled messages performance degrade

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-7340?focusedWorklogId=686194&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-686194 ]

ASF GitHub Bot logged work on AMQ-7340:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Nov/21 03:14
            Start Date: 25/Nov/21 03:14
    Worklog Time Spent: 10m 
      Work Description: lucastetreault removed a comment on pull request #728:
URL: https://github.com/apache/activemq/pull/728#issuecomment-977679810


   Woops, didn't mean to send this yet! 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: gitbox-unsubscribe@activemq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 686194)
    Remaining Estimate: 0h
            Time Spent: 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: Matt Pavlovich
>            Priority: Minor
>         Attachments: ScheduleActiveMQ.zip
>
>          Time Spent: 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.1#820001)