PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/information-schema-innodb-buffer-pool-stats-table.html
NUMBER_READ_AHEAD_EVICTED The number of pages read into the InnoDB buffer pool by the read-ahead background thread that were subsequently evicted without having been accessed by queries. The INNODB_BUFFER_POOL_STATS table provides much of the same ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-innodb-ft-being-deleted-table.html
The INNODB_FT_BEING_DELETED table provides a snapshot of the INNODB_FT_DELETED table; it is used only during an OPTIMIZE TABLE maintenance operation. When OPTIMIZE TABLE is run, the INNODB_FT_BEING_DELETED table is emptied, and DOC_ID values are ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-innodb-ft-config-table.html
The INNODB_FT_CONFIG table provides metadata about the FULLTEXT index and associated processing for an InnoDB table. Before querying it, set the value of the innodb_ft_aux_table system variable to the name (including the database name) of the table ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-innodb-ft-deleted-table.html
The INNODB_FT_DELETED table stores rows that are deleted from the FULLTEXT index for an InnoDB table. Before querying it, set the value of the innodb_ft_aux_table system variable to the name (including the database name) of the table that contains ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-innodb-sys-tablestats-table.html
The INNODB_SYS_TABLESTATS table provides a view of low-level status information about InnoDB tables. This data is used by the MySQL optimizer to calculate which index to use when querying an InnoDB table. This information is derived from in-memory ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-innodb-temp-table-info-table.html
The INNODB_TEMP_TABLE_INFO table is created when first queried, exists only in memory, and is not persisted to disk. The INNODB_TEMP_TABLE_INFO table provides information about user-created InnoDB temporary tables that are active in an InnoDB ...
https://dev.mysql.com/doc/refman/5.7/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/5.7/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 14.9.1.3, “Tuning ...
https://dev.mysql.com/doc/refman/5.7/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/5.7/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 ...