MySQL InnoDB Architecture

Architecture of MySQL Database

Architecture of the InnoDB

Background process effect:

1: Flush data to storage media in a timely manner

2: InnoDB can return to normal when database exception is guaranteed

Very similar to Oracle on the whole

Background process:

1:master Thread

Asynchronously flushes data to disk to ensure consistency of data. including dirty page refresh, merge insert buffer, undo recovery, etc.

2:io Thread

InnoDB Bulk use of AIO (Async io) to process write IO requests, IO thread is primarily responsible for callbacks for these IO requests

The InnoDB 1.0 version consists of 4 io thread:write, read, insert buffer, log IO Thread

The Windows version can be adjusted with the following parameters: Innodb_read_io_threads and innodb_write_io_threads to adjust read and write

#查看当前的InnoDB版本

mysql> SHOW VARIABLES like '%innodb_version% ' \g

#查看参数innodb_write_io_threads

mysql> SHOW VARIABLES like '%innodb_write_io_threads% ' \g

#还可以通过SHOW ENGINE INNODB STATUS \g to see IO Thread

mysql> SHOW ENGINE INNODB STATUS \g

3:purge Thread

Mainly used to reclaim the Undo page, after the thing is submitted, undolog may not use it to recycle.

mysql> SHOW VARIABLES like ' innodb_purge_threads ' \g

　　

Not to be continued ...

MySQL InnoDB Architecture