Eclipse Community Forums: Memory Analyzer » MAT: deadlocks and stalled threads

Help

Home

Home » Eclipse Projects » Memory Analyzer » MAT: deadlocks and stalled threads

Show: Today's Messages :: Show Polls :: Message Navigator

MAT: deadlocks and stalled threads [message #648353]

Wed, 12 January 2011 14:59

Thomas

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.

Report message to a moderator

Re: MAT: deadlocks and stalled threads [message #648381 is a reply to message #648353]

Wed, 12 January 2011 16:27

Jonathan Lawrence

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.

Report message to a moderator

Re: MAT: deadlocks and stalled threads [message #649478 is a reply to message #648381]

Wed, 19 January 2011 12:26

Andrew Johnson

Messages: 205
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.

Report message to a moderator

Previous Topic:	Problem in installing the Eclipse Memory Analyzer
Next Topic:	Stack trace for memory accumulation points

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 10:08:09 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter