Day 53rd: A common way to optimize your site

Small Q: Time, always indifferent, June not see, that the book, full of faint fragrance, even if there are folds, there are scratches, also virtually precipitated the thick of the book.

-----------------------------------------------------------------------------------------------

One: Adjustment of the architecture

With the increase of PV amount, the DB and the Web are separated from one server, and a single db is a web.

Make a squid cache on top of the DB server, or a squid cache on the web;

Load balancer for the Web (LVS + nginx proxy), security considerations with a server to do the high availability of the web, in addition to the DB server implementation of Master-slave, of course, also to find a server to do backup machine, after all, the data is too important;

Second: Optimization of hardware

This is often in the computer room work people know, how much PV, with how much CPU, how much memory, what kind of several cores, how much traffic and so on, how they will be better with the effect;

Three: Optimization of the application itself

Generally we use lamp lnmp, so for L, the optimized object is the kernel parameters, generally we can find development to do, for a and N, we can change the configuration file parameters, or go out of unnecessary modules, Or do an anti-theft chain. Access control. Cache, jump, etc. for M, the main configuration parameters, and p is to change the parameters according to their own needs, for the most commonly used parameters, reduce the unnecessary parameters ...

Four: Optimization of the program

This optimization is mainly for research and development, because the site program is the development of code, and this aspect of direct contact is development, improve code quality, and execution efficiency, but also to optimize our site commonly used methods.

Day 53rd: A common way to optimize your site