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-init-startup-configuration.html
If you have transactions that update, insert, or delete many rows, you might consider increasing the size of the log buffer to save disk I/O. The first decisions to make about InnoDB configuration involve the configuration of data files, log files, ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-introduction.html
With foreign keys, inserts, updates, and deletes are checked to ensure they do not result in inconsistencies across related tables. InnoDB is a general-purpose storage engine that balances high reliability and high performance. Unless you have ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-ddl.html
If this option is set to a value greater than 1, use READ UNCOMMITTED queries to find rows that were just inserted. You can access the underlying InnoDB table (which is test.demo_test by default) through standard SQL interfaces. However, there are ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-developing.html
You might adapt parts of your application that perform single-row queries, inserts, updates, or deletes, to improve performance in critical sections of code. Typically, writing an application for the InnoDB memcached plugin involves some degree of ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-porting-memcached.html
This is because InnoDB performs best for large-scale insertions if primary key values are added in sorted order (as they are with auto-increment values). Primary key values are included in secondary indexes, which takes up unnecessary space if the ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-tuning.html
Benchmarks suggest that queries and DML operations (inserts, updates, and deletes) that use the memcached interface are faster than traditional SQL. Because using InnoDB in combination with memcached involves writing all data to disk, whether ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-migration.html
There are no unmerged insert buffer entries in the .ibd file. This section describes techniques for moving or copying some or all InnoDB tables to a different server or instance. For example, you might move an entire MySQL instance to a larger, ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-monitor-types.html
There are two types of InnoDB monitor: The standard InnoDB Monitor displays the following types of information: Work done by the main background thread Semaphore waits Data about the most recent foreign key and deadlock errors Lock waits for ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-online-ddl-limitations.html
Secondary indexes are not created as efficiently because keys are inserted in the order they appeared in the primary key. The following limitations apply to online DDL operations: The table is copied when creating an index on a TEMPORARY TABLE. The ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-page-compression.html
InnoDB supports page-level compression for tables that reside in file-per-table tablespaces. Page compression is enabled by specifying the COMPRESSION attribute with CREATE TABLE or ALTER TABLE. Supported Platforms Page compression requires sparse ...