It's not a secret anymore!*
The moose likes JBoss/WildFly and the fly likes How to view the performance metrics of Twiddle Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "How to view the performance metrics of Twiddle" Watch "How to view the performance metrics of Twiddle" New topic
Author

How to view the performance metrics of Twiddle

Aliaksei Stasheuski
Greenhorn

Joined: Apr 08, 2011
Posts: 14
Hello to everyone! I'm a novice to JBoss and have some problems/ The problems are that I need to get some metrics through the JMX(just for example : heap memory). Well, It is realized by putting the query to run the twiddle in the powershell script for futher running in SCOMR2. The problem is that twiddle is needed a great time to get the parameters. Can you tell me the reason of the problem? Or the way how can I get the performance metrics and loading sequence of different modules?
Thanks a lot!

Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5823
    
    7

What do you mean by "twiddle is needed a great time"? Are you talking minutes, seconds, hours days?

Also, exactly what data are you asking for that is taking too long.

Twiddle, or a similar JMX call, is what is used by most open source and commercial tools to monitor performance. For example, Nagios uses twiddle.


JBoss In Action
Aliaksei Stasheuski
Greenhorn

Joined: Apr 08, 2011
Posts: 14
Thanks for reply. Well. the time is about a second to get one argument in the jboss.web. The problem is that we need much more arguments to be retrieved through JMX. So we just put the query to start twiddle with a get parameter inside the loop in powershell script. and we want to see output in SCOM in a live time. So if we have for example 10 argunebts in the Mbean to be retrieved we need 10 sec for script to run and this is too long(( And I just need to view the sequence of loading all modules when running the twiddle to watch which of them take the biggest time.
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5823
    
    7

How often are you going to be asking for this information? Most monitoring tools only query this information once every 15 minutes by default. If you ask for it too often you can have a significant performance impact on app server (it can't service as many user requests if you are constantly asking it for data updates).

Of course one of the issues is that each time twiddle is run it has to:
1) load and initialize the JVM
2) establish the connection with the app server
3) request the MBean info
4) clean up and close

Most of the time is spent in the first 2 steps. You could speed things up by either writing your own JMX code (or modifying the twiddle source) to handle multiple MBeans in step 3.
Aliaksei Stasheuski
Greenhorn

Joined: Apr 08, 2011
Posts: 14
Thank you. Peter! I'm already about to writing my own JMX code. But. to tell you the truth. I still want to watch on the performance view of the mentioned four steps, is there any open source tool or just a trial one to make a plots like this: dependency between time to load and the number of step in twiddle loading process. Just for example I want to see some kind of this: The loading of the JVM takes 30 sec, connection takes 15 sec, and so on. Thanks a lot!
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5823
    
    7

Are you asking for something that will give you the times for each of the 4 twiddle steps that I mentioned? There is nothing that I know of, though you could possible modify twiddle to provide that data.
Aliaksei Stasheuski
Greenhorn

Joined: Apr 08, 2011
Posts: 14
Thank you. Peter! I will try to make it this way!
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: How to view the performance metrics of Twiddle