[
https://issues.apache.org/jira/browse/ARTEMIS-2399?focusedWorklogId=277020&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-277020
]
ASF GitHub Bot logged work on ARTEMIS-2399:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 15/Jul/19 22:11
Start Date: 15/Jul/19 22:11
Worklog Time Spent: 10m
Work Description: michaelpearce-gain 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-511587691
@wy96f any chance for higher resolution images? (and whilst at it english
titles to help understand the graphs).
Re impl detail,
As i mentioned in the email lists, i think what ever change is made, as this
is soo core to foundation of the broker, it will be a big and risky change perf
wise, it is key (a must for me) this is something we let people toggle on, and
we leave the default behaviour as was so user dont get suprises and also
de-risks, at least for a few releases, this way if there is a perf issue or
usecase not covered, there wont be any impact to other users.
----------------------------------------------------------------
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: 277020)
Time Spent: 7h 20m (was: 7h 10m)
> 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: 7h 20m
> 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)
