DZone

Engineers use garbage collection logs primarily to troubleshoot memory-related problems and tune their GC settings. However, we are seeing several innovative enterprises using garbage collection logs for following purposes.

1. Lowering AWS Bills

Most applications saturate memory first before saturating other resources (CPU, network bandwidth, storage). Most applications upgrade their EC2 instance size to get additional memory rather than get additional CPU or network bandwidth. With right memory size settings and GC parameters, you can run on basic EC2 instances itself effectively. You don’t have to upgrade to higher EC2 configurations. It can directly cut down your AWS bills. Analyzing GC logs thoroughly will help you to come up with optimal memory size settings.

Source: DZone