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 subversion and git services (JIRA)" <ji...@apache.org> on 2018/07/26 09:43:00 UTC
[jira] [Commented] (AMQ-7021) DestinationMap access inside Abstract
Region readwrite lock does not need sync
[ https://issues.apache.org/jira/browse/AMQ-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558106#comment-16558106 ]
ASF subversion and git services commented on AMQ-7021:
------------------------------------------------------
Commit 0b76d3a0eac9802941b9dfc2a85589dac95ed40a in activemq's branch refs/heads/master from gtully
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=0b76d3a ]
AMQ-7021 - add unsynchronised accessors to destination map for usage with rw lock from abstract region; allow concurrent read of the destination map
> DestinationMap access inside Abstract Region readwrite lock does not need sync
> ------------------------------------------------------------------------------
>
> Key: AMQ-7021
> URL: https://issues.apache.org/jira/browse/AMQ-7021
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 5.16.0
>
>
> Using multiple virtual topic publishers, there is unnecessary serialisation via the destination map.
> the read write lock introduced in AMQ-3454 is sufficient to guard access in this case and reads should operate in parallel.
> with many thousand destinations lookup can be expensive and the serialisation becomes apparent.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)