[jboss-jira] [JBoss JIRA] (WFCORE-161) JMX monitoring is extremely memory inefficient

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on WFCORE-161:
------------------------------------------------

Vaclav Tunka <vtunka at redhat.com> changed the Status of [bug 1154868|https://bugzilla.redhat.com/show_bug.cgi?id=1154868] from MODIFIED to ON_QA

> JMX monitoring is extremely memory inefficient
> ----------------------------------------------
>
>                 Key: WFCORE-161
>                 URL: https://issues.jboss.org/browse/WFCORE-161
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Koen Janssens
>            Assignee: Brian Stansberry
>             Fix For: 1.0.0.Alpha11
>
>
> 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.11#6341)