When dumping data, a large number of disk IO operations and IO are busy, resulting in a relatively high io_wait, which may cause the load to become higher. I guess when your server load is high, the CPU should not be busy at this time, right? If the CPU is idle and IO is busy, it is probably caused by a large amount of IO caused by the dump operation of redis. You can try to optimize the dump-related configuration of redis and try to reduce the dump time interval
High server load is nothing more than insufficient use of a certain resource. CPU resources, disk resources, network resources.
Redis’ dump must have IO operations. Just look at disk read and write.
Since I don’t know the detailed deployment of the original poster, is redis native? Mysql is also native? I feel that mysql is generally not placed on business machines. If it is a high IO load, it should not affect mysql on other machines.
If the number of connections suddenly increases and times out, you can check the number of tcp time_wait. I feel that this is more likely. It is more like a short connection call of a certain service. Once a fault occurs, a large number of time_waits are actively disconnected and network resources are exhausted, causing other services to be unavailable.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
When dumping data, a large number of disk IO operations and IO are busy, resulting in a relatively high io_wait, which may cause the load to become higher. I guess when your server load is high, the CPU should not be busy at this time, right? If the CPU is idle and IO is busy, it is probably caused by a large amount of IO caused by the dump operation of redis. You can try to optimize the dump-related configuration of redis and try to reduce the dump time interval
High server load is nothing more than insufficient use of a certain resource. CPU resources, disk resources, network resources.
Redis’ dump must have IO operations. Just look at disk read and write.
Since I don’t know the detailed deployment of the original poster, is redis native? Mysql is also native? I feel that mysql is generally not placed on business machines. If it is a high IO load, it should not affect mysql on other machines.
If the number of connections suddenly increases and times out, you can check the number of tcp time_wait. I feel that this is more likely. It is more like a short connection call of a certain service. Once a fault occurs, a large number of time_waits are actively disconnected and network resources are exhausted, causing other services to be unavailable.