Search Results
https://dev.mysql.com/doc/refman/8.4/en/innodb-multiple-buffer-pools.html
For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency, by reducing contention as different threads read and write to cached pages. This feature is typically intended for ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-online-ddl-failure-conditions.html
The failure of an online DDL operation is typically due to one of the following conditions: An ALGORITHM clause specifies an algorithm that is not compatible with the particular type of DDL operation or storage engine. A LOCK clause specifies a low ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-online-ddl.html
The online DDL feature provides support for instant and in-place table alterations and concurrent DML. Benefits of this feature include: Improved responsiveness and availability in busy production environments, where making a table unavailable for ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-optimize-tablespace-page-allocation.html
You can optimize how InnoDB allocates space to file-per-table and general tablespaces on Linux. By default, when additional space is required, InnoDB allocates pages to the tablespace and physically writes NULLs to those pages. This behavior can ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-performance-optimizer-statistics.html
This section describes how to configure persistent and non-persistent optimizer statistics for InnoDB tables. Persistent optimizer statistics are persisted across server restarts, allowing for greater plan stability and more consistent query ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-performance-ro-txn.html
InnoDB can avoid the overhead associated with setting up the transaction ID (TRX_ID field) for transactions that are known to be read-only. A transaction ID is only needed for a transaction that might perform write operations or locking reads such ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-performance-spin_lock_polling.html
InnoDB mutexes and rw-locks are typically reserved for short intervals. On a multi-core system, it can be more efficient for a thread to continuously check if it can acquire a mutex or rw-lock for a period of time before it sleeps. If the mutex or ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-performance-thread_concurrency.html
InnoDB uses operating system threads to process requests from user transactions. (Transactions may issue many requests to InnoDB before they commit or roll back.) On modern operating systems and servers with multi-core processors, where context ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-purge-configuration.html
InnoDB does not physically remove a row from the database immediately when you delete it with an SQL statement. A row and its index records are only physically removed when InnoDB discards the undo log record written for the deletion. This removal ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-read-only-instance.html
You can query InnoDB tables where the MySQL data directory is on read-only media by enabling the --innodb-read-only configuration option at server startup. How to Enable To prepare an instance for read-only operation, make sure all the necessary ...