Search Results
https://dev.mysql.com/doc/refman/8.4/en/group-replication.html
However, it is important to understand that if one of the group members becomes unavailable, the clients connected to that group member must be redirected, or failed over, to a different server in the group, using a connector, load balancer, router, ... This chapter explains Group Replication in MySQL 8.4, and how to install, configure and monitor ...
https://dev.mysql.com/doc/refman/8.4/en/gtid-functions.html
It is important to keep in mind that all of these functions take string representations of GTID sets as arguments. The functions described in this section are used with GTID-based replication. As such, the GTID sets must always be quoted when used ...
https://dev.mysql.com/doc/refman/8.4/en/index-statistics.html
For optimizer purposes, an important statistic is the average value group size. Storage engines collect statistics about tables for use by the optimizer. Table statistics are based on value groups, where a value group is a set of rows with the same ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-innodb-tablespaces-table.html
SERVER_VERSION The MySQL version that created the tablespace, or the MySQL version into which the tablespace was imported, or the version of the last major MySQL version upgrade. The INNODB_TABLESPACES table provides metadata about InnoDB ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-processlist-table.html
Important INFORMATION_SCHEMA.PROCESSLIST is deprecated and subject to removal in a future MySQL release. As such, the implementation of SHOW PROCESSLIST which uses this table is also deprecated. It is recommended to use the Performance Schema ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-buffer-pool-flushing.html
When setting a high value it is important to ensure that redo log utilization does not reach 75% (the hardcoded limit at which asynchronous flushing starts), and that the innodb_max_dirty_pages_pct threshold keeps the number of dirty pages to a ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-buffer-pool-optimization.html
Knowing how the InnoDB buffer pool works, and taking advantage of it to keep frequently accessed data in memory, is an important aspect of MySQL tuning. InnoDB maintains a storage area called the buffer pool for caching data and indexes in memory.
https://dev.mysql.com/doc/refman/8.4/en/innodb-buffer-pool.html
Knowing how to take advantage of the buffer pool to keep frequently accessed data in memory is an important aspect of MySQL tuning. The buffer pool is an area in main memory where InnoDB caches table and index data as it is accessed. The buffer ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-internals.html
It is important to minimize the number of times B-tree nodes are split, as well as to minimize the need to uncompress and recompress their content. This section describes some internal implementation details about compression for InnoDB tables. The ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-tuning.html
For some environments, the time it takes to load data can be as important as run-time retrieval. Most often, the internal optimizations described in InnoDB Data Storage and Compression ensure that the system runs well with compressed data. However, ...