You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2018/07/26 09:45:00 UTC

[jira] [Resolved] (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:all-tabpanel ]

Gary Tully resolved AMQ-7021.
-----------------------------
    Resolution: Fixed

A virtual topic send intensive test is ~40% better with the changes b/c matching on the dest map can now operate in parallel as intended by the rw-lock refactor.

Other users of destinationMap still retain the sync get/add semantics

> 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)