[
https://issues.apache.org/jira/browse/ARTEMIS-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176643#comment-16176643
]
ASF GitHub Bot commented on ARTEMIS-1433:
-----------------------------------------
Github user pgfox commented on the issue:
https://github.com/apache/activemq-artemis/pull/1549
@jbertram I have added getAddressMessageUsage as an attribute; in worst
case scenario, if many clients constantly refresh their mBean view, this could
result in a high number of globalSizeBytes.get(). If I understand correctly
globalSizeBytes is on a critical path for the PostOffice.processRoute().
I don't think this change should impact the critical path or have any side
effects .
> expose total Address memory usage in JMX
> ----------------------------------------
>
> Key: ARTEMIS-1433
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1433
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.3.0
> Reporter: Pat Fox
> Priority: Minor
>
> activemq 5.x had a MemoryPercentUsage attribute exposed on the broker MBean
> which showed how much memory was being used by the broker destinations, as a
> percentage of the overall memory.
> Although the memory model in Artemis is different, I think it would still be
> useful to see how much memory the addresses are using in total and also have
> it expressed as a percentage of the global-max-size.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
