MySQL :: MySQL 8.0 Reference Manual

Search Results

Displaying 21 to 30 of 39 total results

10.2.4 Optimizing Performance Schema Queries

https://dev.mysql.com/doc/refman/8.0/en/performance-schema-optimization.html

For additional information about hash indexes, see Section 10.3.9, “Comparison of B-Tree and Hash Indexes”. Applications that monitor databases may make frequent use of Performance Schema tables. To write queries for these tables most ...

6.6.4.5 Obtaining Table Information with myisamchk

https://dev.mysql.com/doc/refman/8.0/en/myisamchk-table-info.html

To obtain a description of a MyISAM table or statistics about it, use the commands shown here. The output from these commands is explained later in this section. myisamchk -d tbl_name Runs myisamchk in “describe mode” to produce a description ...

18.2 The MyISAM Storage Engine

https://dev.mysql.com/doc/refman/8.0/en/myisam-storage-engine.html

Table 18.2 MyISAM Storage Engine Features Feature Support B-tree indexes Yes Backup/point-in-time recovery (Implemented in the server, rather than in the storage engine.) Yes Cluster database support No Clustered indexes No Compressed data Yes ...

18.11.2 The Common Database Server Layer

https://dev.mysql.com/doc/refman/8.0/en/pluggable-storage-common-layer.html

Each storage engine generally has its own indexing methods, although some (such as B-tree indexes) are common to nearly all engines. A MySQL pluggable storage engine is the component in the MySQL database server that is responsible for performing ...

18.5 The ARCHIVE Storage Engine

https://dev.mysql.com/doc/refman/8.0/en/archive-storage-engine.html

The ARCHIVE storage engine produces special-purpose tables that store large amounts of unindexed data in a very small footprint. To enable this storage engine if you build MySQL from source, invoke CMake with the -DWITH_ARCHIVE_STORAGE_ENGINE ...

10.10.2.2 Multiple Key Caches

https://dev.mysql.com/doc/refman/8.0/en/multiple-key-caches.html

For an index assigned to the hot cache, if there are no queries requiring an index scan, there is a high probability that the index blocks corresponding to nonleaf nodes of the index B-tree remain in the cache. Note As of MySQL 8.0, the ...

Chapter 18 Alternative Storage Engines

https://dev.mysql.com/doc/refman/8.0/en/storage-engines.html

Storage engines are MySQL components that handle the SQL operations for different table types. InnoDB is the default and most general-purpose storage engine, and Oracle recommends using it for tables except for specialized use cases. (The CREATE ...

10.10.2.3 Midpoint Insertion Strategy

https://dev.mysql.com/doc/refman/8.0/en/midpoint-insertion.html

The midpoint insertion strategy helps to improve performance when execution of a query that requires an index scan effectively pushes out of the cache all the index blocks corresponding to valuable high-level B-tree nodes. By default, the key cache ...

10.12.3.1 How MySQL Uses Memory

https://dev.mysql.com/doc/refman/8.0/en/memory-use.html

InnoDB uses this variable-size buffering capability to take advantage of row prefetching, and to reduce the overhead of latching and B-tree navigation. MySQL allocates buffers and caches to improve performance of database operations. The default ...

18.2.2 Space Needed for Keys

https://dev.mysql.com/doc/refman/8.0/en/key-space.html

You can roughly calculate the size for the index file as (key_length+4)/0.67, summed over all keys. This is for the worst case when all keys are inserted in sorted order and the table doesn't have any compressed keys. If the first index part is a ...

Displaying 21 to 30 of 39 total results