https://dev.mysql.com/innodb-performance-compression-oltp.html
MySQL uses a variable amount of free space for the pages within each compressed table, only when a designated percentage of compression operations “fail” at runtime, requiring an expensive operation to split the compressed page. Because working ... Traditionally, the InnoDB compression feature was recommended primarily for read-only or read-mostly workloads, such as in a data warehouse ...
https://dev.mysql.com/innodb-performance-optimizer-statistics.html
This section also provides information about estimating ANALYZE TABLE complexity, which may be useful when attempting to achieve a balance between accurate statistics and ANALYZE TABLE execution time. This section describes how to configure ...
https://dev.mysql.com/innodb-performance-ro-txn.html
Eliminating unnecessary transaction IDs reduces the size of internal data structures that are consulted each time a query or data change statement constructs a read view. InnoDB can avoid the overhead associated with setting up the transaction ID ...
https://dev.mysql.com/innodb-purge-configuration.html
When the purge lag exceeds the innodb_max_purge_lag threshold, a delay is imposed on INSERT, UPDATE, and DELETE operations to allow time for purge operations to catch up. InnoDB does not physically remove a row from the database immediately when ...
https://dev.mysql.com/innodb-redo-log.html
With group commit, InnoDB issues a single write to the log file to perform the commit action for multiple user transactions that commit at about the same time, significantly improving throughput. Backup utilities that copy redo log records may ...
https://dev.mysql.com/innodb-restrictions-limitations.html
InnoDB does not keep an internal count of rows in a table because concurrent transactions might “see” different numbers of rows at the same time. This section describes restrictions and limitations of the InnoDB storage engine. You cannot ...
https://dev.mysql.com/innodb-session-temp-tablespaces-table.html
Session temporary tablespaces are recreated each time the server is started. The INNODB_SESSION_TEMP_TABLESPACES table provides metadata about session temporary tablespaces used for internal and user-created temporary tables. The ...
https://dev.mysql.com/innodb-system-tablespace.html
For example, this tablespace has one auto-extending data file: innodb_data_home_dir = innodb_data_file_path = /ibdata/ibdata1:10M:autoextend Suppose that the data file has grown to 988MB over time. The system tablespace is the storage area for the ...
https://dev.mysql.com/innodb-table-import.html
Also, you should export all foreign key related tables at the same logical point in time, as ALTER TABLE ... This section describes how to import tables using the Transportable Tablespaces feature, which permits importing tables, partitioned ...
https://dev.mysql.com/innodb-transaction-scheduling.html
lock_schedule_refreshes The number of times the wait-for graph was analyzed to update the scheduled transaction weights. InnoDB uses the Contention-Aware Transaction Scheduling (CATS) algorithm to prioritize transactions that are waiting for locks.
