This content has been marked as final. Show 3 replies
There are some restrictions on the use of VisualVM, mainly because the Heap Visualiation tools
are based on safepoint that will disrupt the predicatability. The main benefit of VisualVM is to inspect
the Heap, seeing how many Objects of each class exist. This can be done with JavaRTS to inspect
core files, not live processes (but you can easily generate a core from a live process if you don't mind losing predicatability).
On the other hand, if you just want to know more about the amount of memory consumed, you can do much better.
Please have a look at the memory and RTGC related probes in our DTrace provide:
You can easily write a DTrace script to analyze memory consumption WITHOUT disrupting the application.
In fact, you could slightly edit the DTrace scripts coming with TSV to print some user event depending on memory consumption. They will appear on your TSV window:
Feel free to edit these scripts to monitor what you are interested in with very little interference. This is the big benefit of DTrace and TSV !
Feedback is welcome if you'd like to monitor something that is not yet accessible through our DTrace provider.