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/innodb-buffer-pool-in-core-file.html
Excluding buffer pool pages may also be desirable from a security perspective if you have concerns about dumping database pages to core files that may be shared inside or outside of your organization for debugging purposes. A core file records the ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-change-buffer.html
If the working set almost fits in the buffer pool, or if your tables have relatively few secondary indexes, it may be useful to disable change buffering. The change buffer is a special data structure that caches changes to secondary index pages ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-compression-background.html
Because processors and cache memories have increased in speed more than disk storage devices, many workloads are disk-bound. Data compression enables smaller database size, reduced I/O, and improved throughput, at the small cost of increased CPU ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-compression-usage.html
The FILE_BLOCK_SIZE of 8192 requires that the compressed table have a KEY_BLOCK_SIZE of 8. Compressed tables can be created in file-per-table tablespaces or in general tablespaces. The system tablespace (space 0, the .ibdata files) can contain ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-compression.html
Compression can be especially important for SSD storage devices, because they tend to have lower capacity than HDD devices. This section provides information about the InnoDB table compression and InnoDB page compression features. The page ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-configuring-io-capacity.html
Although you can specify a high value such as a million, in practice such large values have little benefit. The InnoDB master thread and other threads perform various tasks in the background, most of which are I/O related, such as flushing dirty ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-consistent-read.html
A consistent read means that InnoDB uses multi-versioning to present to a query a snapshot of the database at a point in time. The query sees the changes made by transactions that committed before that point in time, and no changes made by later or ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-deadlocks-handling.html
This section builds on the conceptual information about deadlocks in Section 17.7.5.2, “Deadlock Detection”. It explains how to organize database operations to minimize deadlocks and the subsequent error handling required in applications.
https://dev.mysql.com/doc/refman/8.0/en/innodb-doublewrite-buffer.html
(The number of buffer pool instances is controlled by the innodb_buffer_pool_instances variable.) Doublewrite file names have the following format: #ib_page_size_file_number.dblwr (or .bdblwr with the DETECT_ONLY setting). The doublewrite buffer is ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-file-space.html
By default, all tablespaces have a page size of 16KB; you can reduce the page size to 8KB or 4KB by specifying the innodb_page_size option when you create the MySQL instance. The data files that you define in the configuration file using the ...