Search Results
https://dev.mysql.com/doc/refman/8.4/en/innodb-file-per-table-tablespaces.html
File-per-table tablespace data files can be created on separate storage devices for I/O optimization, space management, or backup purposes. A file-per-table tablespace contains data and indexes for a single InnoDB table, and is stored on the file ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-system-tables.html
The data in this table is used by the MySQL optimizer to calculate which index to use when querying an InnoDB table. You can extract metadata about schema objects managed by InnoDB using InnoDB INFORMATION_SCHEMA tables. Traditionally, you would ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-temp-table-info.html
It does not provide information about internal InnoDB temporary tables used by the optimizer. INNODB_TEMP_TABLE_INFO provides information about user-created InnoDB temporary tables that are active in the InnoDB instance. mysql> SHOW TABLES FROM ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-introduction.html
InnoDB tables arrange your data on disk to optimize queries based on primary keys. InnoDB is a general-purpose storage engine that balances high reliability and high performance. Unless you have configured a different default storage engine, ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-locking.html
Predicate Locks for Spatial Indexes InnoDB supports SPATIAL indexing of columns containing spatial data (see Section 13.4.9, “Optimizing Spatial Analysis”). Shared and Exclusive Locks Intention Locks Record Locks Gap Locks Next-Key Locks Insert ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-multi-versioning.html
However, if the index condition pushdown (ICP) optimization is enabled, and parts of the WHERE condition can be evaluated using only fields from the index, the MySQL server still pushes this part of the WHERE condition down to the storage engine ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-performance-multiple_io_threads.html
For more information about InnoDB I/O performance, see Section 10.5.8, “Optimizing InnoDB Disk I/O”. InnoDB uses background threads to service various types of I/O requests. You can configure the number of background threads that service read ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-performance-schema.html
This type of tuning is primarily for expert users who evaluate optimization strategies to overcome performance bottlenecks. This section provides a brief introduction to InnoDB integration with Performance Schema. For comprehensive Performance ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-read-only-instance.html
See Section 10.5.3, “Optimizing InnoDB Read-Only Transactions” for ways to tune the performance of read-only queries, which do not require making the entire server read-only. You can query InnoDB tables where the MySQL data directory is on ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-redo-log-buffer.html
For related information, see Memory Configuration, and Section 10.5.4, “Optimizing InnoDB Redo Logging”. The log buffer is the memory area that holds data to be written to the log files on disk. The contents of the log buffer are periodically ...