[
https://issues.apache.org/jira/browse/ARTEMIS-2399?focusedWorklogId=276704&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-276704
]
ASF GitHub Bot logged work on ARTEMIS-2399:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 15/Jul/19 13:20
Start Date: 15/Jul/19 13:20
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-511398767
@michaelandrepearce I deployed the test without MAX_DEPAGE_NUM limit during
depage. The performance result as follows:
1. Running in 51MB size page and 1 page cache in the case of 100 multicast
queues. The consumer tps dropped to ~11000 compared to ~16000 in pr.
2. Running in 5MB size page and 100 page cache in the case of 100 multicast
queues. The consumer tps dropped to ~10000 compared to ~15000 in pr.
3. Running in 51MB size page and 1 page cache in the case of 1 queue.
Performance results similar.
Seems like paged message removed and re reading file resulted in the
performance drop particularly in the case of heavy usage of memory(test #1,#2).
Even if there was enough free memory and messages were not gced(test #3), the
performance didn't make a big difference - instead memory footprint might be
increased. Considering we've totally relied on the kernel page cache, it seems
not to need spare messages in memory. I personally assume this is an import
feature.
----------------------------------------------------------------
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: 276704)
Time Spent: 6h 50m (was: 6h 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: 6h 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)
