[
https://issues.apache.org/jira/browse/ARTEMIS-3771?focusedWorklogId=760264&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-760264
]
ASF GitHub Bot logged work on ARTEMIS-3771:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 21/Apr/22 17:50
Start Date: 21/Apr/22 17:50
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on PR #4023:
URL:
https://github.com/apache/activemq-artemis/pull/4023#issuecomment-1105525758
@clebertsuconic @franz1981
Restored the cache to previous behavior, this PR now primarily just gets rid
of the binding-query which was the real performance sink anyway.
Don't really know how to write a meaningful test to demonstrate the benefit
though, but the easiest way to "real-life" demonstrate it is by loading the
broker with thousands of queues and have a single producer send messages in
individual sessions (such as some frameworks unfortunately tend to do it).
Issue Time Tracking
-------------------
Worklog Id: (was: 760264)
Time Spent: 1.5h (was: 1h 20m)
> Rework destination handling for the OpenWire-protocol
> -----------------------------------------------------
>
> Key: ARTEMIS-3771
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3771
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Anton Roskvist
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Rework destination handling for the OpenWire-protocol
>
> Mainly improves things for brokers with many destinations and for handling
> clients not reusing JMS resources, but should be a nice overall improvement
> for OpenWire.
> Changes are:
> openWireDestinationCache now global, also taking over the role for the
> connection destination cache
> Avoid calling BindingQuery since that method is expensive when dealing with a
> large number of destinations
> openwireDestinationCacheSize no longer has to be a power of 2
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
