Shulou(Shulou.com)05/31 Report--

How to understand the database server layer of the public MySQL, I believe that many inexperienced people do not know what to do about it. Therefore, this paper summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

The MySQL plug-in storage engine is a component of the MySQL database server, which is responsible for performing actual data I / O operations for the database, and can allow and enforce a specific set of features for special application requirements. One of the main advantages of using a special storage engine is that it only needs to provide the characteristics required for special applications, so the system overhead in the database is less, and the end result is more efficient and higher database performance. This is one of the reasons why MySQL is always considered to have high performance, and it can match or beat proprietary monolithic databases in terms of industry standard benchmarks.

From a technical point of view, what are some unique components that support the underlying structure in the storage engine? Some key differences include:

Concurrency: some applications have more granular locking requirements (such as row-level locking) than others. Choosing the right locking strategy can reduce overhead and help improve overall performance. It also includes support for multiple capabilities, such as multi-version concurrency control or "snapshot" reading.

Transaction support: not all applications require transactions, but for those that do, there are well-defined requirements, such as ACID compatibility.

Referential integrity: with foreign keys defined by DDDL, the server needs to force the referential integrity of the associated database.

Physical storage: it includes a variety of things, from the total page size of tables and indexes to the format needed to store data, to physical disks.

Index support: different applications tend to adopt different indexing strategies, and each storage engine usually has its own indexing method, but some indexing methods (such as B-tree indexes) are common to almost all storage engines.

Memory caching: different applications respond better to certain memory caching strategies than other applications, so while some memory caches are common to all storage engines (such as caching for user connections, MySQL's cache query caching, etc.), other caching strategies are only defined when a particular storage engine is used.

Performance help: including multi-I _ hand O threads for parallel operations, thread concurrency, database checkpoints, batch insert processing, etc.

Other target features: may include support for geospatial operations, security restrictions on specific data processing operations, etc.

Each set of basic components of the plug-in storage engine is designed to provide an optional set of features for specific applications. On the other hand, avoiding the use of component feature sets can help avoid unnecessary overhead. Therefore, it is obvious that you should understand the set of requirements for a particular application and choose the appropriate MySQL storage engine that can significantly improve the overall efficiency and performance of the system.

After reading the above, have you mastered how to understand the database server layer of the public MySQL? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.