[
https://issues.apache.org/jira/browse/AMQ-7340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17294663#comment-17294663
]
Matt Pavlovich commented on AMQ-7340:
-------------------------------------
Please provide version of ActiveMQ and the configuration file. Also, please
specify the CPU and memory allocation for the Docker or Kubernetes
configuration.
Reminder-- Java processes generally should not be configured to use less than 1
CPU and generally should have 2 to 4 CPU for optimal balance of throughput and
number of total instances.
> 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
> Priority: Minor
>
> 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.3.4#803005)
