[jboss-jira] [JBoss JIRA] (WFLY-3889) JMX monitoring is extremely memory inefficient

[Kabir Khan (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006617#comment-13006617 ] 

Kabir Khan commented on WFLY-3889:
----------------------------------

Seems the PR was done by Brian, not Jeff :-)

> JMX monitoring is extremely memory inefficient
> ----------------------------------------------
>
>                 Key: WFLY-3889
>                 URL: https://issues.jboss.org/browse/WFLY-3889
>             Project: WildFly
>          Issue Type: Bug
>          Components: Domain Management, JMX
>    Affects Versions: JBoss AS7 7.1.1.Final, 9.0.0.Alpha1
>            Reporter: Koen Janssens
>            Assignee: Brian Stansberry
>
> When reading any JMX attribute(s), I have noticed a noticeable impact on the performance of our system. After attaching a profiler, I see that getting a single attribute of a JMX bean (either using remoting or using jconsole) is generating thousands of objects, that have to cleaned up by the GC. For instance, 6000 instances of the ModelNode class are created.
> A clone is made of the complete management model before executing any JMX operation. This happens in the OperationContextImpl.readResourceFromRoot class.
> More background on associated forum thread



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)