Search Results
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-background.html
Because processors and cache memories have increased in speed more than disk storage devices, many workloads are disk-bound. Data compression enables smaller database size, reduced I/O, and improved throughput, at the small cost of increased CPU ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-configuration.html
This section provides configuration information and procedures for InnoDB initialization, startup, and various components and features of the InnoDB storage engine. For information about optimizing database operations for InnoDB tables, see Section ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-deadlock-detection.html
When deadlock detection is enabled (the default), InnoDB automatically detects transaction deadlocks and rolls back a transaction or transactions to break the deadlock. InnoDB tries to pick small transactions to roll back, where the size of a ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-doublewrite-buffer.html
The doublewrite buffer is a storage area where InnoDB writes pages flushed from the buffer pool before writing the pages to their proper positions in the InnoDB data files. If there is an operating system, storage subsystem, or unexpected mysqld ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-innodb_cmpmem.html
The INNODB_CMPMEM and INNODB_CMPMEM_RESET tables provide status information about compressed pages that reside in the buffer pool. Please consult Section 17.9, “InnoDB Table and Page Compression” for further information on compressed tables and ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-tables.html
For related information and examples, see Section 17.15, “InnoDB INFORMATION_SCHEMA Tables”. INFORMATION_SCHEMA InnoDB tables can be used to monitor ongoing InnoDB activity, to detect inefficiencies before they turn into issues, or to ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-temp-table-info.html
INNODB_TEMP_TABLE_INFO provides information about user-created InnoDB temporary tables that are active in the InnoDB instance. It does not provide information about internal InnoDB temporary tables used by the optimizer. mysql> SHOW TABLES FROM ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-transactions.html
Each transaction in InnoDB that is waiting for another transaction to release a lock (INNODB_TRX.TRX_STATE is LOCK WAIT) is blocked by exactly one blocking lock request. That blocking lock request is for a row or table lock held by another ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-linux-native-aio.html
InnoDB uses the asynchronous I/O subsystem (native AIO) on Linux to perform read-ahead and write requests for data file pages. This behavior is controlled by the innodb_use_native_aio configuration option, which applies to Linux systems only and is ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-moving-data-files-offline.html
The innodb_directories variable, which defines directories to scan at startup for tablespace files, supports moving or restoring tablespace files to a new location while the server is offline. During startup, discovered tablespace files are used ...