[
https://issues.apache.org/jira/browse/ARTEMIS-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy A. Bish resolved ARTEMIS-5893.
--------------------------------------
Fix Version/s: 2.52.0
Resolution: Fixed
> Optimize ManagementService
> --------------------------
>
> Key: ARTEMIS-5893
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5893
> Project: Artemis
> Issue Type: Improvement
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Fix For: 2.52.0
>
>
> Currently
> {{org.apache.activemq.artemis.core.server.management.impl.ManagementServiceImpl}}
> has a single instance of a {{java.util.Map}} to manage _every single_
> management object. In high-volume use-cases this map might contains millions
> of entries. This can slow down management operations on particular resources
> (e.g. addresses or queues) because the broker has to look through the whole
> map to gather and report on that particular resource.
> Performance could be improved by partitioning each resource type into its own
> map. This will reduce the overall time needed to gather, filter, etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
