Java Memory Management Performance Analysis: Difference between revisions
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
Full collection frequency, time and CPU usage: | Full collection frequency, time and CPU usage: | ||
gc event-type:FULL_COLLECTION -o collection-time ./gc.log > | gc event-type:FULL_COLLECTION -o collection-time ./gc.log > full-collection-time.csv | ||
New generation collection frequency, time, and CPU usage: | |||
gc event-type:YOUNG_GENERATION_COLLECTION -o collection-time ./gc.log > new-generation-collection-time.csv | |||
=Leak Analysis= | =Leak Analysis= | ||
{{Internal|YourKit Operations#Memory_Snapshot_Comparison|YourKit Memory Snapshot Comparison}} | {{Internal|YourKit Operations#Memory_Snapshot_Comparison|YourKit Memory Snapshot Comparison}} | ||
Latest revision as of 15:25, 31 August 2017
Internal
Old Generation Analysis
Old generation occupancy after full collections. This is the primary indicator of memory leaks.
gc event-type:FULL_COLLECTION -o old-after, old-capacity, heap-capacity ./gc.log > gc.csv
Garbage Collection Time Analysis
Full collection frequency, time and CPU usage:
gc event-type:FULL_COLLECTION -o collection-time ./gc.log > full-collection-time.csv
New generation collection frequency, time, and CPU usage:
gc event-type:YOUNG_GENERATION_COLLECTION -o collection-time ./gc.log > new-generation-collection-time.csv