Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Memory Analyzer » MAT: deadlocks and stalled threads
MAT: deadlocks and stalled threads [message #648353] Wed, 12 January 2011 14:59 Go to next message
Thomas  is currently offline Thomas Friend
Messages: 1
Registered: January 2011
Junior Member
Hello
I am comparing Memory Analyzer with JProbe.

JProbe is claiming to be able to pinpoint code bottlenecks, deadlocks and stalled threads. See below.

Is this something that Memory Analyzer can perform as well?

Thanks in advance,
Thomas

JProbe Performance Performance analysis tool can help you quickly pinpoint and diagnose the
underlying root cause of code bottlenecks and thread contentions. It can help you to quickly locate and
repair inefficient code that creates bottlenecks, deadlocks and stalled threads that can lead to slow overall
performance and cripple scalability.
Re: MAT: deadlocks and stalled threads [message #648381 is a reply to message #648353] Wed, 12 January 2011 16:27 Go to previous messageGo to next message
Jonathan Lawrence is currently offline Jonathan LawrenceFriend
Messages: 16
Registered: July 2009
Junior Member
These capabilities would be more in the domain of the Java Health Center tool, which is provided as a feature of IBM Support Assistant.

http://www.ibm.com/software/support/isa/

Memory Analyzer would not be suitable for these investigations as such.
Re: MAT: deadlocks and stalled threads [message #649478 is a reply to message #648381] Wed, 19 January 2011 12:26 Go to previous message
Andrew Johnson is currently offline Andrew JohnsonFriend
Messages: 142
Registered: July 2009
Senior Member
[quote title=Jonathan Lawrence wrote on Wed, 12 January 2011 16:27]These capabilities would be more in the domain of the Java Health Center tool, which is provided as a feature of IBM Support Assistant.

Please note that IBM Monitoring and Diagnostic Tools for Java - Health Center is only for IBM VMs.

Eclipse Memory Analyzer works with a snapshot of the state of a VM, which has all the heap objects, classes, etc. It does not do continuous monitoring of a system. It was designed for solving memory leaks, and is also good at seeing where memory is wasted, and can be used to find the state of a system for debugging. It doesn't measure performance as such.
Previous Topic:Problem in installing the Eclipse Memory Analyzer
Next Topic:Stack trace for memory accumulation points
Goto Forum:
  


Current Time: Wed Nov 14 00:32:47 GMT 2018

Powered by FUDForum. Page generated in 0.01509 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top