Shulou(Shulou.com)06/01 Report--

This article mainly shows you "what the InnoDB architecture is like". The content is simple and clear. I hope it can help you solve your doubts. Let the editor lead you to study and learn this article "what the InnoDB architecture is like."

The overall architecture of InnoDB includes a buffer pool composed of multiple memory and multiple background threads.

The cache pool caches hard disk data (to solve the serious mismatch between CPU speed and disk speed). The background process ensures the consistency of cache pool and hard disk data, and ensures that the data can be restored to normal state in case of abnormal downtime.

The cache pool consists of three parts: redo log buffer,innodb_buffer_pool,innodb_additional_mem_pool.

Redo log buffer: cache the redo log.

Innodb_buffer_pool: cache data, index information.

Innodb_additional_mem_pool: cache LRU linked lists, etc.

Background threads include master thread,IO thread,purge thread,page cleaner thread.

Master thread: responsible for flushing cached data to the hard disk.

IO thread: handles callbacks such as insert buffer, redo logs, read and write requests, etc.

Purge thread: recycle undo pages.

Page cleaner thread: refresh dirty pages.

InnoDB internal coordination management

When a SQL enters the MySQL server, it goes through the connection pool module (authenticating and generating threads), query cache module (whether it has been cached or not), SQL interface module (simple syntax verification), query parsing module, optimizer module (generating syntax tree), and then enters the InnoDB storage engine module. At this point, I have written the last part of the process just now, so I will mention it at once.

After entering the InnoDB, we will first determine whether the pages involved in the SQL exist in the cache. Note that the MySQL loads the corresponding pages from the hard disk into memory each time and carries out related operations. If it does not exist, load the data into the cache.

Second, if it is a select statement, the relevant statement is read and the query result is returned to the value server. If it is a update,insert,delete statement, read the relevant page and first try to give the record shackles involved in the SQL.

Then, after the lock is successful, write the undo page first, logically record the status of these records before modification, and then modify the relevant records, these operations will be synchronized to redo log buffer, and then generate a new log.

Finally, the modification is completed and the dirty data is refreshed to the hard disk.

These are all the contents of the article "what is the InnoDB Architecture?" Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

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.