Then, I opened a new window and requested it once more
Here, I'm curious about the CPU not going to 200%. It's been between 120% and 130%. P.S. I must not have a solid knowledge of something, otherwise, I wouldn't have this doubt.
II. Heap space
Since there are no JVM heap space issues involved, executing jstat -gcutil 32593 1s didn't see anything wrong. 32593 is the java process ID and 1s means 1 second sampling.
The heap is fine, just see which thread is high occupied.
List the threads of the java process, top -H -p
willjvm a warehousedump be over (of a period of time) jstack -l >> stack.log， Here I choose3596。
In the log, to find the corresponding thread, we need to find the corresponding thread from the stack log, but since the stack log uses hexadecimal, but the PID in top is again in decimal. So, it is necessary to manually convert the PID from decimal to hexadecimal. The hexadecimal turn of 3596 is 0xe0c