[
https://issues.apache.org/jira/browse/ARTEMIS-2399?focusedWorklogId=288714&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-288714
]
ASF GitHub Bot logged work on ARTEMIS-2399:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Aug/19 07:10
Start Date: 05/Aug/19 07:10
Worklog Time Spent: 10m
Work Description: franz1981 commented on issue #2750: ARTEMIS-2399
Improve performance when there are a lot of subscribers
URL: https://github.com/apache/activemq-artemis/pull/2750#issuecomment-518114338
@michaelandrepearce
> which test?
Just a specific scenario I've been fallen into recently, to summarize it:
- a topic with many publishers sending durable messages
- many durable subscribers
- 1 of the subscribers disconnect for some time
- publishers start paging
- after 10 GB of paged data, the subscriber come back online again
- while it catches up, the other publishers/subscribers rate are seriously
affected (approaching to 1/2 msg/sec)
- when it catches up, things come back normal for everyone
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 288714)
Time Spent: 14h 50m (was: 14h 40m)
> Improve performance when there are a lot of subscribers
> -------------------------------------------------------
>
> Key: ARTEMIS-2399
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2399
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.9.0
> Environment: broker 2.9.0
> cpu: 4 cores, memory: 8G, disk: ssd 500G
> broker.xml:
> <thread-pool-max-size>60</thread-pool-max-size>
> <address-setting match="#">
> <max-size-bytes>51Mb</max-size-bytes>
> <page-size-bytes>50Mb</page-size-bytes>
> <page-max-cache-size>1</page-max-cache-size>
> <address-full-policy>PAGE</address-full-policy>
> </address-setting>
> <message-expiry-scan-period>-1</message-expiry-scan-period>
> Reporter: yangwei
> Priority: Major
> Time Spent: 14h 50m
> Remaining Estimate: 0h
>
> We noticed that there was a significant drop in performance when entering
> page mode in the case of multiple subscribers.
> We created a topic and 100 queues bound to it. We ran our _GrinderRunner
> test_ in our inner test infra cluster with 500 threads producing message and
> 560 threads, each one picked a random queue to subscribe. The test showed
> performance is bad: 13000 msg/s sent and 5000 msg/s received.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
