MySQL optimization approximate direction

1: From SQL and Index direction (most basic)

To do this, you can use the tool mysqldumpslow that comes with MySQL, or you can use a third-party tool to pt-query-digest this more carefully

Second: From the table structure direction

Specific operation: A is the table field selection (can exist when the content of the selection of small fields, occupy a smaller space), a whether to follow the third paradigm, B is the vertical direction of the segmentation (large-scale paragraph is unreasonable, put into a table), Horizontal direction segmentation (data volume is larger), the problem is in the statistics of the joint query problem According to the specific business, sub-foreground and backstage, the day before yesterday to improve speed, query the data inside the table, and then the statistical report when the query does not slice the table data

Third: From the operating system line of defense

For example, 32-bit operating system, 64-bit operating system, the maximum limit for each file, 32-bit operating system seems to be the maximum 2G, and 64-bit unlimited, as well as firewalls and so on

IV: Configuration of MySQL database parameters, such as setting the buffer pool size, and how long the buffer pool is flushed to disk configuration, etc.

The above is from the MySQL performance optimization approach, personal understanding

V: Extend the hardware, extend the cup, memory, simple and rough practice, but the cost is the highest, the effect is not the most obvious way

MySQL optimization approximate direction