Tengyou Bian Xiao recently met a customer and asked how to solve the problem Nginx server CPU alarm, red and other problems occur frequently in configuration. Today's article, Micron Network Edge, sorts out the preliminary solutions for you. I hope it can help you to meet the 100% CPU solution when you meet the NGINX server. Generally, when you configure the NGINX server, CPU alarms often appear, which is caused by the php cache and blocking. Sites with daily IP addresses less than 10000 can basically be defaulted, and users with daily IP addresses greater than 100 million can understand the situation.

First investigate the possibility of customer problems:

Because the website traffic is too large and the IP number is over one million, the CPU will increase to 100% of the running rate crazily, leading to the server crash. After several days of research, one result is that connection congestion leads to infinite cycle collapse. After each collapse, it can be blocked again about 2-3 hours after restart. According to the programmer's analysis, the traffic may exceed the delay, leading to a crash.

Then, encounter Nginx server ? What is the solution for configuring frequent CPU alerts

First, you need to determine whether the server configuration is sufficient. This user uses BGP server, and whether the broadband and configuration are sufficient. E5-2650V4 * 232G memory and 250G Samsung solid state disk can confirm that the configuration is correct. The problem is that the system is not optimized, and nginx debugging is not good, but it is relieved after debugging.

Finally, Micronet Bianxiao suggests that enterprise users:

If you find that the server configuration of NGINX often alerts the CPU, which is mostly caused by connection congestion and MYSQL conflict, it is recommended to separate PHP and MYSQL, which has the best effect! OK, thank you for your support. If you need a server, please visit the official website of Micronet for relevant information. thank you!