PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 295.2Kb
Man Pages (Zip)
- 400.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-table-reference.html
The following table summarizes all available Performance Schema tables. For greater detail, see the individual table descriptions. Table 29.1 Performance Schema Tables Table Name Description accounts Connection statistics per client account ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-wait-tables.html
These tables store wait events: events_waits_current: The current wait event for each thread. There are also summary tables that aggregate information about wait events; see Section 29.12.20.1, “Wait Event Summary Tables”. For more information ... The Performance Schema instruments waits, which are events that take ...
https://dev.mysql.com/doc/refman/8.0/en/repair-table-optimization.html
An alternative that avoids this problem is to use a separate key cache, assign to it the indexes from the table to be repaired, and deallocate it when the repair is complete. REPAIR TABLE for MyISAM tables is similar to using myisamchk for repair ...You may be able to its improve performance by setting these variables, as described in Section 6.6.4.6, “myisamchk Memory ...
https://dev.mysql.com/doc/refman/8.0/en/thread-pool-information-schema-tables.html
Note As of MySQL 8.0.14, the INFORMATION_SCHEMA thread pool tables are also available as Performance Schema tables. (See Section 29.12.16, “Performance Schema Thread Pool Tables”.) The INFORMATION_SCHEMA tables are deprecated; expect them be ...
https://dev.mysql.com/doc/refman/8.0/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. To dig deeper into performance considerations for ... Overall application performance, CPU and I/O utilization and the size of disk files are good indicators of how effective compression is for your ...
https://dev.mysql.com/doc/refman/8.0/en/fulltext-fine-tuning.html
To rebuild FULLTEXT indexes for an InnoDB table, use ALTER TABLE with the DROP INDEX and ADD INDEX options to drop and re-create each index. To rebuild the FULLTEXT indexes for a MyISAM table, it is sufficient to do a QUICK repair operation: mysql> ...Do not alter the MySQL sources unless you know what you are ...You can exert more control over full-text searching behavior if you have a MySQL source ...
https://dev.mysql.com/doc/refman/8.0/en/cost-model.html
These estimates are stored in the server_cost and engine_cost tables in the mysql system database and are configurable at any time. The intent of these tables is to make it possible to easily adjust the cost estimates that the optimizer uses when it ... To generate execution plans, the optimizer uses a cost model that is based on estimates of the cost of various operations that occur during query ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-innodb-cached-indexes-table.html
The INNODB_CACHED_INDEXES table reports the number of index pages cached in the InnoDB buffer pool for each index. For related usage information and examples, see Section 17.15.5, “InnoDB INFORMATION_SCHEMA Buffer Pool Tables”. row ...Index ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-innodb-tablespaces-brief-table.html
The INNODB_TABLESPACES_BRIEF table provides space ID, name, path, flag, and space type metadata for file-per-table, general, undo, and system tablespaces. INNODB_TABLESPACES provides the same metadata but loads more slowly because other metadata ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-table-info.html
The table_info table provides information about logging, checkpointing, distribution, and storage options in effect for individual NDB tables.