Search



Search Results
Displaying 1591 to 1600 of 1802 total results
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-usage.html
The actual compression algorithm is not affected by the KEY_BLOCK_SIZE value; the value determines how large each compressed chunk is, which in turn affects how many rows can be packed into each compressed page. Compressed tables can be created in ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-disk-management.html
Organizing tables into many small files, a few larger files, or a combination of both. 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 ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-compression-tables.html
There are two pairs of InnoDB INFORMATION_SCHEMA tables about compression that can provide insight into how well compression is working overall: INNODB_CMP and INNODB_CMP_RESET provide information about the number of compression operations and the ...INNODB_CMPMEM and INNODB_CMPMEM_RESET provide information about the way memory is allocated for ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-internal-data.html
The data exposed by the transaction and locking tables (INFORMATION_SCHEMA INNODB_TRX table, Performance Schema data_locks and data_lock_waits tables) represents a glimpse into fast-changing data. This is not like user tables, where the data ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-tables.html
INFORMATION_SCHEMA InnoDB tables can be used to monitor ongoing InnoDB activity, to detect inefficiencies before they turn into issues, or to troubleshoot performance and capacity issues. For related information and examples, see Section 17.15, ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-understanding-innodb-locking.html
For a lock to be acquired by a transaction, all incompatible lock requests previously entered into the lock queue for that row or table must be removed (which occurs when the transactions holding or requesting those locks either commit or roll back). When a transaction updates a row in a table, or locks it with SELECT FOR UPDATE, InnoDB establishes a list or queue of locks on that ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-multiple-buffer-pools.html
For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency, by reducing contention as different threads read and write to cached pages. This feature is typically intended for ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-online-ddl-space-requirements.html
Each temporary sort file is large enough to hold one column of data, and each sort file is removed when its data is merged into the final table or index. Disk space requirements for online DDL operations are outlined below. The requirements do not ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-table-import.html
As a faster way of moving data than importing a dump file, which requires reinserting data and rebuilding indexes. Otherwise, the table must be created on the same MySQL server instance into which it is being imported. This section describes how to ...
https://dev.mysql.com/doc/refman/8.4/en/installing-development-tree.html
This section describes how to install MySQL from the latest development source code, which is hosted on GitHub. To obtain the MySQL Server source code from this repository hosting service, you can set up a local MySQL Git repository. On GitHub, ...
Displaying 1591 to 1600 of 1802 total results