[
https://issues.apache.org/jira/browse/ARTEMIS-2399?focusedWorklogId=282405&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-282405
]
ASF GitHub Bot logged work on ARTEMIS-2399:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 25/Jul/19 02:57
Start Date: 25/Jul/19 02:57
Worklog Time Spent: 10m
Work Description: wy96f 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-514875375
> I will need some time to review this last week.
>
> Can you rebase again after I merged your change?
I'm working on PageReader per queue these days. Unluckily some problem was
encountered. After investigation, I found it was related to #2740 which would
sync files while closing. Given we put PageReader in PageSubscription meaning
100 times of file open/close for each page in our case(100 queues), although
page file is only opened for reading, the sync operation does cause great
performance loss - ~5000 msg/s received and 13000 msg/s sent now compared with
16000 msg/s received and 11000 msg/s sent of pr. Should I file a new jira and
pr to fix the problem introuduced by #2740 or just fix it in this one?
----------------------------------------------------------------
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: 282405)
Time Spent: 13h (was: 12h 50m)
> 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: 13h
> 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)
