Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.9.0
-
None
-
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>
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>
Description
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.
