]
Kabir Khan updated WFLY-3889:
-----------------------------
Assignee: Brian Stansberry (was: Jeff Mesnil)
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