Capture the Garbage Collection log from the application suffering from high CPU consumption.

This is one of the primary reasons for the CPU to spike up all of sudden. This cycle will continue, causing the Garbage collection to run again and again, which will cause the CPU to spike up. So JVM will trigger Garbage collection once again. Now JVM will once again check whether memory usage is high because Garbage collection didn’t free up any memory space. Garbage Collection will complete its run, but the Garbage Collection process won’t be able to free up the memory, as the objects are actively referenced. Once the application’s memory usage hits the threshold point, Garbage Collection is triggered. When an application is suffering from a memory leak, it will continuously create objects without releasing them. But what causes Garbage Collection to run repeatedly? Garbage Collection is a computation-intensive operation, as it requires marking, sweeping, compacting, and relocating objects in the memory. When Garbage Collection repeatedly runs in the JVM, CPU consumption will start to spike. This type of sudden CPU spike usually happens because of two reasons: This article talks about how to troubleshoot these kinds of sudden CPU spikes. After recycling, the application might be running fine for a few hours (or a few minutes depending on your karma :-)) before the CPU consumption starts to spike up.ĭoes this pattern sound familiar? :-). The only way to recover from this problem is to recycle the application. Even if you remove the server from load balancer (so that traffic isn’t sent anymore), still the CPU consumption is maxed out. Your Java application has been running fine, but all of a sudden CPU consumption starts to go higher and higher until it stays at 80 – 100%. We have devised a better and simpler strategy to troubleshoot CPU spikes in this article.

Windows monitor cpu spikes