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-memcached-setup.html
Note Before setting up the daemon_memcached plugin, consult Section 14.21.4, “Security Considerations for the InnoDB memcached Plugin” to understand the security procedures required to prevent unauthorized access. Installing and Configuring the ... This section describes how to set up the daemon_memcached plugin on a MySQL ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-innodb-cluster-introduction.html
This chapter introduces MySQL InnoDB Cluster, which combines MySQL technologies to enable you to deploy and administer a complete integrated high availability solution for MySQL. This content is a high-level overview of InnoDB Cluster, for full ...
https://dev.mysql.com/doc/refman/5.7/en/optimizing-innodb-diskio.html
Increase buffer pool size When table data is cached in the InnoDB buffer pool, it can be accessed repeatedly by queries without requiring any disk I/O. Specify the size of the buffer pool with the innodb_buffer_pool_size option. This memory area is ... If you follow best practices for database design and tuning techniques for SQL operations, but your database is still slow due to heavy disk I/O activity, consider these disk I/O ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-introduction.html
InnoDB is a general-purpose storage engine that balances high reliability and high performance. Unless you have configured a different default storage engine, issuing a CREATE TABLE statement without an ENGINE clause creates an InnoDB table. Key ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-standard-monitor.html
Standard Monitor output is limited to 1MB when produced using the SHOW ENGINE INNODB STATUS statement. Example Standard Monitor output: mysql> SHOW ENGINE INNODB STATUS\G *************************** 1. The number of seconds is the elapsed time ...
https://dev.mysql.com/doc/refman/5.7/en/optimizing-innodb-configuration-variables.html
Because the InnoDB storage engine performs many of its optimizations automatically, many performance-tuning tasks involve monitoring to ensure that the database is performing well, and changing configuration options when performance drops. See ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-benefits.html
InnoDB tables have the following benefits: If the server unexpectedly exits because of a hardware or software issue, regardless of what was happening in the database at the time, you don't need to do anything special after restarting the database.
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-porting-mysql.html
If there is a short numeric primary key column in an InnoDB table, use it as the unique lookup key for memcached by converting the integer to a string value. If the memcached server is used for multiple applications, or with more than one InnoDB ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-thread_concurrency.html
InnoDB uses operating system threads to process requests from user transactions. (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 ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-compression-internals.html
This section describes some internal implementation details about compression for InnoDB tables. Note Prior to MySQL 5.7.24, InnoDB supports the zlib library up to version 1.2.3. In MySQL 5.7.24 and later, InnoDB supports the zlib library up to ...