Another interesting thing i am seeing is how the heap memory just drops
(which I think is due to garbage collection but not certain). If you hit
garbage collection manually it will peg the CPU and drop the heap memory to
a lower which is why i think it is.
In the attached picture the heap memory
Something I've been monitoring lately is heap memory because it can cause a
lot of problems if you hit the JVM max memory limit. Usually what happens
when you do is GarbageCollection will run when it hits the max memory and it
will peg one of the cores on the CPU to 100%. That causes client
