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-check-availability.html
Issue the SHOW ENGINES statement to view the available MySQL storage engines.
https://dev.mysql.com/doc/refman/5.7/en/innodb-introduction.html
InnoDB tables arrange your data on disk to optimize queries based on primary keys. InnoDB is a general-purpose storage engine that balances high reliability and high performance. Unless you have configured a different default storage engine, ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-dml.html
Benchmarks suggest that the daemon_memcached plugin speeds up DML operations (inserts, updates, and deletes) more than it speeds up queries. Therefore, consider focussing initial development efforts on write-intensive applications that are ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-intro.html
The innodb_api_trx_level configuration option controls the transaction isolation level on queries processed by memcached. The InnoDB memcached plugin implements memcached as a MySQL plugin daemon that accesses the InnoDB storage engine directly, ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-troubleshoot.html
These limits primarily apply if you intend to create an index on a value column to run report-generating queries on that column using SQL. This section describes issues that you may encounter when using the InnoDB memcached plugin. If you encounter ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-midpoint_insertion.html
In mixed workloads where most of the activity is OLTP type with periodic batch reporting queries which result in large scans, setting the value of innodb_old_blocks_time during the batch runs can help keep the working set of the normal workload in ... Rather than using a strict LRU algorithm, InnoDB uses a technique to minimize the amount of data that is brought into the buffer pool and never accessed ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-purge-configuration.html
InnoDB does not physically remove a row from the database immediately when you delete it with an SQL statement. A row and its index records are only physically removed when InnoDB discards the undo log record written for the deletion. This removal ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-system-tablespace.html
The system tablespace is the storage area for the InnoDB data dictionary, the doublewrite buffer, the change buffer, and undo logs. It may also contain table and index data if tables are created in the system tablespace rather than file-per-table ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html
Isolation is the I in the acronym ACID; the isolation level is the setting that fine-tunes the balance between performance and reliability, consistency, and reproducibility of results when multiple transactions are making changes and performing ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-model.html
InnoDB performs locking at the row level and runs queries as nonlocking consistent reads by default, in the style of Oracle. The InnoDB transaction model aims combine the best properties of a multi-versioning database with traditional two-phase ...