Hello Taouj!
Greetings.
Your GC behaviour looks normal. From 3:05pm - 3:15pm there is spike in memory consumption. This can cause the CPU spike as well. But it also settles down after 3:15pm.
Inorder to accurately point the lines of code causing the CPU spike, you need to analyze thread dumps and 'top -H -p {PID}' command output, where {PID} is your Java application's process Id which is experiencing CPU spike. When you issue this ‘top’ command with given arguments, it will list all the threads running in the application and amount of CPU each one of the thread consume. Once you have both the data, you can identify high CPU consuming thread and lines of code they are executing. You can either capture these artifacts and analyze them manually, or use the 14 day trial version of yCrash tool. yCrash tool automatically captures application-level data (thread dump, heap dump, Garbage Collection log) and system-level data (netstat, vmstat, iostat, top, top -H, dmesg,...). It marries these two datasets and generates an instant root cause analysis report pointing out exact line of code causing the CPU spike. Here is more information on how to diagnose high CPU spike.
Edit your Comment