PDF (US Ltr)
- 41.9Mb
PDF (A4)
- 42.0Mb
Man Pages (TGZ)
- 272.3Kb
Man Pages (Zip)
- 378.3Kb
Info (Gzip)
- 4.2Mb
Info (Zip)
- 4.2Mb
Search Results
https://dev.mysql.com/doc/refman/9.7/en/innodb-information-schema-examples.html
This section describes the use of locking information as exposed by the Performance Schema data_locks and data_lock_waits tables. Identifying Blocking Transactions It is sometimes helpful to identify which transaction blocks another. The tables ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-locking.html
Shared and Exclusive Locks Intention Locks Record Locks Gap Locks Next-Key Locks Insert Intention Locks AUTO-INC Locks Predicate Locks for Spatial Indexes Shared and Exclusive Locks InnoDB implements standard row-level locking where there are two ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-online-ddl-performance.html
Online DDL improves several aspects of MySQL operation: Applications that access the table are more responsive because queries and DML operations on the table can proceed while the DDL operation is in progress. Reduced locking and waiting for MySQL ...
https://dev.mysql.com/doc/refman/9.7/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/9.7/en/innodb-page-compression.html
InnoDB supports page-level compression for tables that reside in file-per-table tablespaces. Page compression is enabled by specifying the COMPRESSION attribute with CREATE TABLE or ALTER TABLE. Supported Platforms Page compression requires sparse ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-performance-compression-oltp.html
Traditionally, the InnoDB compression feature was recommended primarily for read-only or read-mostly workloads, such as in a data warehouse configuration. The rise of SSD storage devices, which are fast but relatively small and expensive, makes ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-performance-midpoint_insertion.html
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 again. The goal is to make sure that frequently accessed (“hot”) pages remain in the buffer ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-performance-multiple_io_threads.html
InnoDB uses background threads to service various types of I/O requests. You can configure the number of background threads that service read and write I/O on data pages using the innodb_read_io_threads and innodb_write_io_threads configuration ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-persistent-stats.html
The persistent optimizer statistics feature improves plan stability by storing statistics to disk and making them persistent across server restarts so that the optimizer is more likely to make consistent choices each time for a given query.
https://dev.mysql.com/doc/refman/9.7/en/innodb-physical-structure.html
With the exception of spatial indexes, InnoDB indexes are B-tree data structures. Spatial indexes use R-trees, which are specialized data structures for indexing multi-dimensional data. Index records are stored in the leaf pages of their B-tree or ...