-
1. Re: JMX monitoring is extremely memory inefficient
dlofthouse Sep 22, 2014 7:58 AM (in response to janssk77)Could you please confirm which attribute you are reading when you see this? Is this the attribute from an MBean or a JMX representation of the management model?
-
2. Re: JMX monitoring is extremely memory inefficient
ctomc Sep 22, 2014 9:18 AM (in response to janssk77)Also can you try with EAP 6.3 as there ware lots of changes in that area around 6.2+ times.
-
3. Re: JMX monitoring is extremely memory inefficient
janssk77 Sep 22, 2014 10:46 AM (in response to dlofthouse)I'm reading an attribute from the jboss.as domain. it does not really matter which one as long as it comes from the jboss.as domain.
eg: attribute serverState of jboss.as:management-root=server
I have not tried with another server, but looking at the latest code in github, the clone still happens.
The first thing the MBean server does is finding a delegate. In that process, it already creates a clone of the whole management model. Once it finds the delegate, it gets the actual attribute, creating another clone of the mgnt model..
-
4. Re: JMX monitoring is extremely memory inefficient
ctomc Sep 22, 2014 7:14 PM (in response to janssk77)And again I would ask you if you can test with newer code as this part has changed considerably.
Try with either EAP 6.3 or with WildFly 8.1 or even better WildFly 9 alpha1 we released last week.
-
5. Re: JMX monitoring is extremely memory inefficient
janssk77 Sep 23, 2014 12:31 AM (in response to ctomc)Tried with wildfly 9 alpha1
The cloning of the management model still happens. Since the management model of an empty jboss is not that big, the overhead is small.
However, once more things are configured (queues/datasources), I'm afraid the cloning will become a bottleneck again...
-
6. Re: JMX monitoring is extremely memory inefficient
ctomc Sep 23, 2014 6:13 AM (in response to janssk77)Any chance you can file bug report in WildFly jira for this https://issues.jboss.org/browse/WFLY
-
8. Re: JMX monitoring is extremely memory inefficient
ctomc Sep 25, 2014 9:48 AM (in response to janssk77)Proposed solution https://github.com/wildfly/wildfly-core/pull/199