Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

There's a lot of documentation out there on how to use the 'jvisualvm' profiler, but very little (if any) real-life advice on how to analyze all those charts and dumps. I'm just a little overwhelmed by all the graphs and having trouble making sense of it all.

I know this is sort of a monolithic-type question, but there has to be a way to condense its typical uses into a fairly concise list - finding memory leaks, zombie threads and such.

What specifically are some of the common analyses for VisualVM?

share|improve this question
up vote 0 down vote accepted

What specifically are some of the common analyses for VisualVM?

I think these are the same as for any other Java profiler. For example, YourKit profiler demos page currently lists the following "most popular" analyses:

  • CPU profiling
  • J2EE profiling
  • Finding a memory leak
  • Profiling excessive garbage allocations
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.