Search Results
https://dev.mysql.com/doc/mysql-monitor/8.0/en/mem-ui-settings-data-purge-ref.html
This includes all data collections, including CPU, memory and connections and activity statistics. This includes all data collections, including CPU, memory and connections and activity statistics. This includes all data collections, including CPU, ... Data Purge Behavior enables you to automatically remove old data from the repository according to a ...
https://dev.mysql.com/doc/heatwave/en/heatwave-status-variables.html
Column-level statistics are collected for tables on the MySQL DB System during a cluster size estimate. Data is tracked in megabytes and is a cumulative total of data scanned since the MySQL HeatWave Cluster was last started. The counter is reset to ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-advisor-auto-query-time-estimation.html
Retrieve detailed statistics using the query below The query retrieves detailed statistics from the heatwave_autopilot_report table. For an example of the detailed statistics, see Run Auto Query Time Estimation. Auto Query Time Estimation provides: ...
https://dev.mysql.com/doc/refman/8.4/en/binary-log-transaction-compression.html
The statistics include the data compression ratio for the monitored period, and you can also view the effect of compression on the last transaction on the server. Statistics for binary logs and relay logs are split out so you can see the impact of ... MySQL supports binary log transaction compression; when this is enabled, transaction payloads are compressed using the zstd algorithm, and then written to the server's binary log file as a single event (a ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-replication-group-member-stats.html
Statistics regarding the certifier and applier procedures are useful to understand how the applier queue is growing, how many conflicts have been found, how many transactions were checked, which transactions are committed everywhere, and so on. The ... Each member in a replication group certifies and applies transactions received by the ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-innodb-cmp-per-index-table.html
The INNODB_CMP_PER_INDEX and INNODB_CMP_PER_INDEX_RESET tables provide status information on operations related to compressed InnoDB tables and indexes, with separate statistics for each combination of database, table, and index, to help you ...For ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-innodb_cmpmem.html
The INNODB_CMP and INNODB_CMP_RESET tables should provide more useful statistics on compression. The INNODB_CMPMEM and INNODB_CMPMEM_RESET tables have identical contents, but reading from INNODB_CMPMEM_RESET resets the statistics on relocation ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-online-ddl-operations.html
Setting persistent table statistics options ALTER TABLE tbl_name STATS_PERSISTENT=0, STATS_SAMPLE_PAGES=20, STATS_AUTO_RECALC=1, ALGORITHM=INPLACE, LOCK=NONE; Only modifies table metadata. For more information, see Section 17.8.10.1, “Configuring ... Online support details, syntax examples, and usage notes for DDL operations are provided under the following topics in this ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-nutshell.html
Added a number of status variables specific to the Group Replication plugin that improve diagnosis and troubleshooting of network instabilities, providing statistics about network usage, control messages, and data messages for each group member. In ... This section summarizes what has been added to, deprecated in, changed, and removed from MySQL 8.4 since MySQL ...
https://dev.mysql.com/doc/refman/8.4/en/optimizing-innodb-many-tables.html
If you have configured non-persistent optimizer statistics (a non-default configuration), InnoDB computes index cardinality values for a table the first time that table is accessed after startup, instead of storing such values in the table. This ...