You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/04/08 13:24:00 UTC
[jira] [Work logged] (ARTEMIS-3771) Rework destination handling for the OpenWire-protocol
[ https://issues.apache.org/jira/browse/ARTEMIS-3771?focusedWorklogId=754582&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-754582 ]
ASF GitHub Bot logged work on ARTEMIS-3771:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 08/Apr/22 13:23
Start Date: 08/Apr/22 13:23
Worklog Time Spent: 10m
Work Description: AntonRoskvist opened a new pull request, #4023:
URL: https://github.com/apache/activemq-artemis/pull/4023
This gives a significant performance increase for my use case but I could not find a good way to demonstrate it through testing, so the added tests only focus on functionality
Issue Time Tracking
-------------------
Worklog Id: (was: 754582)
Remaining Estimate: 0h
Time Spent: 10m
> 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: 10m
> 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.1#820001)