A real server performance optimization

This kind of server optimization is really not encountered, and nothing is optimized in the end. At the beginningProgramAnd data on a server. When the number of online users exceeds six hundred, the server's eating and access will be slow. The number of people keeps increasing. Apache's CPU reaches 100%. Chilling. I have never seen such a running status. Optimized Apache performance configuration. CPU usage drops. However, access is still slow. Enlarge tables_caches of MySQL. The increase in the number of people to nine hundred is still the same slow. There is no major problem with the query procedure. Database problems. The system has no data since it was launched. The CPU usage and memory usage of MySQL are not high. Add a server. Ten did not expect that the number of people on the other server with the same configuration went online to one thousand four hundred, and the access was normal and fast. In the beginning, a server could not afford to grow to six hundred servers. Ah. Chilling!

It is a database problem. The CPU and memory of the database are not high. And when server access is slow. The operation and login on the other server are both fast. It is an Apache problem. Why is it okay that Apache can grow to one thousand four hundred people. If the business logic is complicated, we still need to separate the database from the program! Check the problem. Program maintenance! In addition, broadband sometimes puts pressure on the server!

This lesson is really profound. Be careful and careful later! This is another abnormal development peak. Port the system to the Linux operating system within one day. RedHat has never been operated. I used Ubuntu only. However, the company's server cannot install ubuntu. Even the redhat4.0 and later operating systems cannot be installed. 3.4.6 is installed. Development is to help others clean up the mess! Use what others give!

There are many lessons learned this time. It's not long! Have feelings!