Search Results
https://dev.mysql.com/doc/refman/8.4/en/innodb-configuration.html
For information about optimizing database operations for InnoDB tables, see Section 10.5, “Optimizing for InnoDB Tables”. This section provides configuration information and procedures for InnoDB initialization, startup, and various components ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-disk-management.html
Within these constraints, InnoDB tries to optimize the database work and the organization of disk files to minimize the amount of disk I/O. As a DBA, you must manage disk I/O to keep the I/O subsystem from becoming saturated, and manage disk space ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-fulltext-index.html
To remove full-text index entries for deleted records, run OPTIMIZE TABLE on the indexed table with innodb_optimize_fulltext_only=ON to rebuild the full-text index. Full-text indexes are created on text-based columns (CHAR, VARCHAR, or TEXT ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-index-types.html
To get the best performance from queries, inserts, and other database operations, it is important to understand how InnoDB uses the clustered index to optimize the common lookup and DML operations. For guidelines to take advantage of InnoDB ... Each ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-init-startup-configuration.html
The first decisions to make about InnoDB configuration involve the configuration of data files, log files, page size, and memory buffers, which should be configured before initializing InnoDB. Modifying the configuration after InnoDB is initialized ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-online-ddl-limitations.html
OPTIMIZE TABLE for an InnoDB table is mapped to an ALTER TABLE operation to rebuild the table and update index statistics and free unused space in the clustered index. OPTIMIZE TABLE is supported with the addition of online DDL support for ... The ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-performance-read_ahead.html
For more information about I/O performance, see Section 10.5.8, “Optimizing InnoDB Disk I/O” and Section 10.12.1, “Optimizing Disk I/O”. A read-ahead request is an I/O request to prefetch multiple pages in the buffer pool asynchronously, in ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-temporary-tablespace.html
Session Temporary Tablespaces Session temporary tablespaces store user-created temporary tables and internal temporary tables created by the optimizer when InnoDB is configured as the storage engine for on-disk internal temporary tables. A maximum ... InnoDB uses session temporary tablespaces and a global temporary ...
https://dev.mysql.com/doc/refman/8.4/en/kill.html
Warning Killing a REPAIR TABLE or OPTIMIZE TABLE operation on a MyISAM table results in a table that is corrupted and unusable. Any reads or writes to such a table fail until you optimize or repair it again (without interruption). KILL [CONNECTION ...
https://dev.mysql.com/doc/refman/8.4/en/load-data.html
For information about the efficiency of INSERT versus LOAD DATA and speeding up LOAD DATA, see Section 10.2.5.1, “Optimizing INSERT Statements”. The file can be read from the server host or the client host, depending on whether the LOCAL ...