Search Results
https://dev.mysql.com/doc/refman/8.4/en/information-schema-innodb-metrics-table.html
InnoDB counts only those transactions that it executes, whereas Performance Schema collects events for all non-aborted transactions initiated by the server, including empty transactions. The INNODB_METRICS table provides a wide variety of InnoDB ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-innodb-tables-table.html
For related usage information and examples, see Section 17.15.3, “InnoDB INFORMATION_SCHEMA Schema Object Tables”. The INNODB_TABLES table has these columns: TABLE_ID An identifier for the InnoDB table. NAME The name of the table, preceded by ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-user-attributes-table.html
The access control system has not been initialized (for example, the server was started with the --skip-grant-tables option). The USER_ATTRIBUTES table provides information about user comments and user attributes. The USER_ATTRIBUTES table has ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-buffer-pool-flushing.html
Buffer pool flushing is initiated when the percentage of dirty pages reaches the low water mark value defined by the innodb_max_dirty_pages_pct_lwm variable. InnoDB performs certain tasks in the background, including flushing of dirty pages from ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-change-buffer.html
You can enable or disable buffering for inserts, delete operations (when index records are initially marked for deletion) and purge operations (when index records are physically deleted). The change buffer is a special data structure that caches ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-tuning-monitoring.html
This section builds on the performance tuning advice from Section 17.9.1.3, “Tuning Compression for InnoDB Tables”, and shows how to find problems that might not turn up during initial testing. Overall application performance, CPU and I/O ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-usage.html
Compressed tables can be created in file-per-table tablespaces or in general tablespaces. The system tablespace (space 0, the .ibdata files) can contain user-created tables, but it also contains internal system data, which is never compressed.
https://dev.mysql.com/doc/refman/8.4/en/innodb-configuration.html
This section provides configuration information and procedures for InnoDB initialization, startup, and various components and features of the InnoDB storage engine. For information about optimizing database operations for InnoDB tables, see Section ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-create-table-external.html
There are different reasons for creating InnoDB tables externally; that is, creating tables outside of the data directory. Those reasons might include space management, I/O optimization, or placing tables on a storage device with particular ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-file-per-table-tablespaces.html
Initial file-per-table tablespace extensions are by small amounts, after which extensions occur in increments of 4MB. A file-per-table tablespace contains data and indexes for a single InnoDB table, and is stored on the file system in a single data ...