Search Results
https://dev.mysql.com/doc/refman/8.4/en/information-schema-optimization.html
Applications that monitor databases may make frequent use of INFORMATION_SCHEMA tables. To write queries for these tables most efficiently, use the following general guidelines: Try to query only INFORMATION_SCHEMA tables that are views on data ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-partitions-table.html
Each row in this table corresponds to an individual partition or subpartition of a partitioned table. The PARTITIONS table has these columns: TABLE_CATALOG The name of the catalog to which the table belongs. TABLE_SCHEMA The name of the schema ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-change-buffer.html
The change buffer is a special data structure that caches changes to secondary index pages when those pages are not in the buffer pool. The buffered changes, which may result from INSERT, UPDATE, or DELETE operations (DML), are merged later when ...
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
This section builds on the conceptual information about deadlocks in Section 17.7.5.2, “Deadlock Detection”. It explains how to organize database operations to minimize deadlocks and the subsequent error handling required in applications.
https://dev.mysql.com/doc/refman/8.4/en/innodb-file-space.html
The data files that you define in the configuration file using the innodb_data_file_path configuration option form the InnoDB system tablespace. You cannot define where within the system tablespace your tables are allocated. In a newly created ...
https://dev.mysql.com/doc/refman/8.4/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.4/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/8.4/en/innodb-performance-spin_lock_polling.html
InnoDB mutexes and rw-locks are typically reserved for short intervals. 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 ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-performance-thread_concurrency.html
InnoDB uses operating system threads to process requests from user transactions. (Transactions may issue many requests to InnoDB before they commit or roll back.) On modern operating systems and servers with multi-core processors, where context ...