The overall structure of MySql
MySQL consists of connection pool, SQL interface, parser, optimizer, cache, storage Engine, etc., can be divided into three layers, namely the MySQL Server layer, the storage engine layer and the file system layer. The MySQL Server layer includes the connection layer and the SQL layer. The following is the infrastructure diagram of MySQL in the official documentation:
#In the above figure, Connection pool is the connection layer, Management Services & Utilities...Caches & Buffers is the SQL layer, and Pluggable Storage Engines is the storage engine layer, and File system, Files & Logs are the file system layer.
Connectors do not belong to any of the above layers. Connectors can be understood as various clients and application services, mainly referring to the interaction between different languages and SQL.
Related free learning recommendations: mysql video tutorial
1. Connection layer
The application connects to MySQL through interfaces (such as ODBC, JDBC), and the first connection processing is the connection layer. The connection layer includes three parts: communication protocol, thread processing, and user name and password authentication.
Connection Pool belongs to the connection layer. Since it takes a lot of time to establish a connection every time, the role of the connection pool is to cache user connections, user names, passwords, permission verification, thread processing and other needs that need to be cached. Next time, you can directly use the established connection. Improve server performance.
2. SQL layer
The SQL layer is the core of MySQL, and MySQL’s core services are implemented in this layer. It mainly includes permission judgment, query cache, parser, preprocessing, query optimizer, cache and execution plan.
Management Services & Utilities, SQL Interface, Parser, Optimizer, and Caches & Buffers belong to the SQL layer, as detailed in the following table.
Name | Description |
---|---|
## System management and control tools for #MySQL, including backup and recovery, MySQL replication, clustering, and more. | |
is used to receive the user's SQL command and return the results that the user needs to query. For example, SELECT FROM calls the SQL Interface. | |
When the SQL command is passed to the parser, it will be verified and parsed by the parser so that the MySQL optimizer can recognize the data structure Or return an error for the SQL statement. | |
The SQL statement will use the query optimizer to optimize the query before querying, and at the same time verify whether the user has permission to query, and the cache Is the latest data available? It uses a "select-project-join" strategy for querying. For example, | SELECT id, name FROM student WHERE gender = "female"; In the statement, the SELECT query first selects based on the WHERE statement, instead of querying the entire table and then filtering by gender. The SELECT query first performs attribute projection based on id and name, instead of extracting all attributes and then filtering, and connects these two query conditions to generate the final query result.
|
If the query cache has a hit query result, the query statement can directly fetch data from the query cache. This caching mechanism is composed of a series of small caches, such as table cache, record cache, key cache, permission cache, etc. |
The above is the detailed content of Detailed explanation of the overall structure of MySql. For more information, please follow other related articles on the PHP Chinese website!