Search Results
https://dev.mysql.com/doc/refman/8.4/en/information-schema-tp-thread-state-table.html
Note The INFORMATION_SCHEMA thread pool tables are deprecated, and subject to removal in a future version of MySQL. You should use the versions available as Performance Schema tables instead. Applications should transition away from the old tables ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-benchmarking.html
Alternatively, to run test queries and other statements without disturbing the original table, make a copy: CREATE TABLE ... If InnoDB is not the default storage engine, you can determine if your database server and applications work correctly with ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-tuning-monitoring.html
Overall application performance, CPU and I/O utilization and the size of disk files are good indicators of how effective compression is for your application. This section builds on the performance tuning advice from Section 17.9.1.3, “Tuning ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-deadlocks-handling.html
Add well-chosen indexes to your tables so that your queries scan fewer index records and set fewer locks. Use EXPLAIN SELECT to determine which indexes the MySQL server regards as the most appropriate for your queries. This section builds on the ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-disk-management.html
As a DBA, you must manage disk I/O to keep the I/O subsystem from becoming saturated, and manage disk space to avoid filling up storage devices. The ACID design model requires a certain amount of I/O that might seem redundant, but helps to ensure ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-file-defragmenting.html
Random insertions into or deletions from a secondary index can cause the index to become fragmented. Fragmentation means that the physical ordering of the index pages on the disk is not close to the index ordering of the records on the pages, or ...
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. How the Clustered Index Speeds Up Queries Accessing ... Each InnoDB table has a special index called the clustered index that stores row ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-internal-data.html
The data exposed by the transaction and locking tables (INFORMATION_SCHEMA INNODB_TRX table, Performance Schema data_locks and data_lock_waits tables) represents a glimpse into fast-changing data. This is not like user tables, where the data ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-linux-native-aio.html
InnoDB uses the asynchronous I/O subsystem (native AIO) on Linux to perform read-ahead and write requests for data file pages. This behavior is controlled by the innodb_use_native_aio configuration option, which applies to Linux systems only and is ...
https://dev.mysql.com/doc/refman/8.4/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 ...