1. Check CPU usage:

Run the top command to query the system CPU usage and idle time. The third line of the output shows CPU usage statistics: user processes (us), system processes (sy), processes with custom nice values (ni), and idle time (id). Pay attention to the us and wa values. The wa value indicates the percentage of time CPU waits for IO operations to complete. A large wa value indicates a disk IO bottleneck.

2. Find processes that consume excessive CPU resources:

Run the top command to query the processes that consume excessive CPU resources.

Run the ps aux | grep <process name> command to view the CPU usage of a specific process.

3. Analyze the cause for excessive CPU usage:

Check whether processes consuming excessive CPU resources are abnormal, checking for issues such as infinite loops, inefficient algorithms, and memory leaks.

For more information about service processes, see the relevant logs.

4. Check the system load:

Run the uptime or vmstat command to query the average system load. If the load stays high, there may be too many concurrent processes or significant contention among them. Check the relationship between these processes and stop unnecessary processes or minimize resource contention.