PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/innodb-file-format-compatibility-checking.html
To prevent possible crashes or data corruptions when InnoDB opens an ib-file set, it checks that it can fully support the file formats in use within the ib-file set. If the system is restarted following a crash, or a “fast shutdown” (i.e., ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-tuning.html
Because using InnoDB in combination with memcached involves writing all data to disk, whether immediately or sometime later, raw performance is expected to be somewhat slower than using memcached by itself. When using the InnoDB memcached plugin, ...Benchmarks suggest that queries and DML operations (inserts, updates, and deletes) that use the memcached interface are faster than traditional ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-physical-structure.html
With the exception of spatial indexes, InnoDB indexes are B-tree data structures. The page size is determined by the innodb_page_size setting when the MySQL instance is initialized. When new records are inserted into an InnoDB clustered index, ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-restrictions-limitations.html
This section describes restrictions and limitations of the InnoDB storage engine. You cannot create a table with a column name that matches the name of an internal InnoDB column (including DB_ROW_ID, DB_TRX_ID, and DB_ROLL_PTR. mysql> CREATE TABLE ...This restriction applies to use of the names in any ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb-innodb-engines.html
The NDB storage engine is implemented using a distributed, shared-nothing architecture, which causes it to behave differently from InnoDB in a number of ways. For those unaccustomed to working with NDB, unexpected behaviors can arise due to its ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-buffer-pool-optimization.html
InnoDB maintains a storage area called the buffer pool for caching data and indexes in memory. 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.
https://dev.mysql.com/doc/refman/5.7/en/innodb-checkpoints.html
(Strictly speaking, this performance improvement is available for MySQL 5.1 with the InnoDB Plugin 1.0.7 and higher. It is with MySQL 5.5 that this improvement is available in the default InnoDB storage engine.) How Checkpoint Processing Works ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-examples.html
The tables that contain information about InnoDB transactions and data locks enable you to determine which transaction is waiting for another, and which resource is being requested. (For descriptions of these tables, see Section 14.16.2, “InnoDB ... Identifying Blocking Transactions It is sometimes helpful to identify which transaction blocks ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-metrics-table.html
The INNODB_METRICS table provides information about InnoDB performance and resource-related counters. SET GLOBAL innodb_monitor_disable = [counter-name|module_name|pattern|all]; innodb_monitor_reset: Resets counter values to zero. SET GLOBAL ...For ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema.html
This section provides information and usage examples for InnoDB INFORMATION_SCHEMA tables. InnoDB INFORMATION_SCHEMA tables provide metadata, status information, and statistics about various aspects of the InnoDB storage engine. You can view a list ...For general information regarding the MySQL INFORMATION_SCHEMA database, see Chapter 24, INFORMATION_SCHEMA ...