-
Optimize indexes, SQL statements, analyze slow queries;
-
Design the database strictly according to the design paradigm of the database;
-
You can save disk IO by using memcache caching, and placing frequently accessed data in the Memcache cache without the need for frequently changing data;
-
Optimize hardware, adopt SSD, use Disk Queue technology (RAID0,RAID1,RDID5), etc.
-
Using MySQL internal table partitioning technology, the data layer different files, can improve the efficiency of disk reading;
-
Vertical sub-table; Put some infrequently read data in a table, save disk I/O;
-
The master-slave separation reads and writes, and the read and write operations of the database are separated by the master-slave replication;
-
Sub-database sub-table sub-machine (data volume is particularly large), the main principle is data routing;
-
Select the appropriate table engine and optimize the parameters;
-
Architecture-level caching, static and distributed;
-
Do not use full-text indexing;
-
Use faster storage, such as NoSQL storage for frequently accessed data
This article is from the "Hello I am Forest" blog, please make sure to keep this source http://chensenlin.blog.51cto.com/10559465/1875193
A common method of MySQL database optimization