PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 296.5Kb
Man Pages (Zip)
- 401.9Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/innodb-change-buffer.html
Merging cached changes at a later time, when affected pages are read into the buffer pool by other operations, avoids substantial random access I/O that would be required to read secondary index pages into the buffer pool from disk. During this ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-compression-tuning-monitoring.html
To dig deeper into performance considerations for compressed tables, you can monitor compression performance at runtime using the Information Schema tables described in Example 17.1, “Using the Compression Information Schema Tables”. This ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-deadlocks-handling.html
You can cope with deadlocks and reduce the likelihood of their occurrence with the following techniques: At any time, issue SHOW ENGINE INNODB STATUS to determine the cause of the most recent deadlock. In particular, do not leave an interactive ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-file-space.html
(These segments are different from the rollback segment, which actually contains many tablespace segments.) When a segment grows inside the tablespace, InnoDB allocates the first 32 pages to it one at a time. InnoDB can add up to 4 extents at a time ... The data files that you define in the configuration file using the innodb_data_file_path configuration option form the InnoDB system ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-next-key-locking.html
The so-called phantom problem occurs within a transaction when the same query produces different sets of rows at different times. For example, if a SELECT is executed twice, but returns a row the second time that was not returned the first time, ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-performance-midpoint_insertion.html
The pages are moved to the front of the list (the most-recently used end) when they are accessed in the buffer pool for the first time. In these scans, a data page is typically accessed a few times in quick succession and is never touched again. The ... Rather than using a strict LRU algorithm, InnoDB uses a technique to minimize the amount of data that is brought into the buffer pool and never accessed ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-performance-spin_lock_polling.html
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 rw-lock becomes available during this period, the thread can continue ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-performance-thread_concurrency.html
In situations where it is helpful to minimize context switching between threads, InnoDB can use a number of techniques to limit the number of concurrently executing operating system threads (and thus the number of requests that are processed at any ... InnoDB uses operating system threads to process requests from user ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-preload-buffer-pool.html
In addition to saving the buffer pool state at shutdown and restoring it at startup, you can save and restore the buffer pool state at any time, while the server is running. If the operation is complete, the completion time is printed (e.g. If the ... To reduce the warmup period after restarting the server, InnoDB saves a percentage of the most recently used pages for each buffer pool at server shutdown and restores these pages at server ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-tablespace-autoextend-size.html
By default, when a file-per-table or general tablespace requires additional space, the tablespace is extended incrementally according to the following rules: If the tablespace is less than an extent in size, it is extended one page at a time. If ...