Search

GC easy – Universal Java GC Log Analyser

Tag

Consecutive full GC

INCREASE THROUGHPUT

Throughput measures productive work done by an application over time, distinguishing it from non-productive tasks such as garbage collection (GC). If 2 minutes out of 60 minutes are spent on GC, throughput drops to 96.67%. Poor throughput can result from long GC pauses, memory leaks, consecutive full GCs, or resource contention.

ELIMINATE CONSECUTIVE FULL GCs

Full GC in JVM is crucial for memory management but can severely impact application performance due to high CPU consumption and application thread pauses. Consecutive full GCs typically indicate insufficient heap size allocation. Solutions include increasing JVM heap size, enhancing Perm Gen/metaspace size, or adding more JVM instances. Validation is essential.

Up ↑