3 years ago

Those artifacts are: In this article, let's try to understand these 3 critical artifacts, where to use them, how do they look, how to capture them, how to analyze them, and their differences.

It will indicate how many GC events ran, what type of GC events they are (i.e. Young GC or Full GC), how long each GC event pause the application, how much objects did each GC event reclaim.

Here is the command that you need to issue to capture thread dump: where pid: is the Process Id of the application, whose thread dump should be captured file-path: is the file path where thread dump will be written in to.

Heap dump files are in binary format and tend to be large in size.