PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndb-innodb-workloads.html
A number of major differences in behavior between the NDB and InnoDB storage engines with regard to some common types of database-driven application workloads are shown in the following table:: Table 25.3 Differences between InnoDB and NDB storage ... NDB Cluster has a range of unique attributes that make it ideal to serve applications requiring high availability, fast failover, high throughput, and low ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-deadlocks.html
If frequent deadlocks highlight a problem with transaction structure or application error handling, enable innodb_print_all_deadlocks to print information about all deadlocks to the mysqld error log. When deadlock detection is enabled (the default) ... A deadlock is a situation in which multiple transactions are unable to proceed because each transaction holds a lock that is needed by another ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-checkpoints.html
Then InnoDB scans the log files forward from the checkpoint, applying the logged modifications to the database. InnoDB flushes modified database pages from the buffer pool in small batches. During crash recovery, InnoDB looks for a checkpoint label ...It often makes sense to set the total size of the log files as large as the buffer pool or even ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-innodb-cluster-introduction.html
InnoDB Cluster uses the following MySQL technologies: MySQL Shell, which is an advanced client and code editor for MySQL. The following diagram shows an overview of how these technologies work together: Figure 23.1 InnoDB Cluster overview Being ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-information-schema-temp-table-info.html
Create a simple InnoDB temporary table: mysql> CREATE TEMPORARY TABLE t1 (c1 INT PRIMARY KEY) ENGINE=INNODB; Query INNODB_TEMP_TABLE_INFO to view the temporary table metadata. mysql> SELECT * FROM INFORMATION_SCHEMA.INNODB_TEMP_TABLE_INFO\G An empty ... INNODB_TEMP_TABLE_INFO provides information about user-created InnoDB temporary tables that are active in the InnoDB ...row ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-performance-thread_concurrency.html
(Transactions may issue many requests to InnoDB before they commit or roll back.) On modern operating systems and servers with multi-core processors, where context switching is efficient, most workloads run well without any limit on the number of ...
https://dev.mysql.com/doc/refman/8.0/en/optimizing-innodb-ddl-operations.html
Online DDL support for adding secondary indexes means that you can generally speed up the process of creating and loading a table and associated indexes by creating the table without secondary indexes, then adding secondary indexes after the data is ... Many DDL operations on tables and indexes (CREATE, ALTER, and DROP statements) can be performed ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-performance-optimizer-statistics.html
You can query optimizer statistics data in the mysql.innodb_table_stats and mysql.innodb_index_stats tables. You can manually modify the mysql.innodb_table_stats and mysql.innodb_index_stats tables to force a specific query optimization plan or to ...Persistent optimizer statistics also provide control and flexibility with these additional benefits: You can use the innodb_stats_auto_recalc configuration option to control whether statistics are updated automatically after substantial changes to a ...
https://dev.mysql.com/doc/refman/8.0/en/optimizing-innodb-many-tables.html
If you have configured non-persistent optimizer statistics (a non-default configuration), InnoDB computes index cardinality values for a table the first time that table is accessed after startup, instead of storing such values in the table. This ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-performance-read_ahead.html
InnoDB uses two read-ahead algorithms to improve I/O performance: Linear read-ahead is a technique that predicts what pages might be needed soon based on pages in the buffer pool being accessed sequentially. You control when InnoDB performs a ... A ...