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-internals.html
mysql> USE innodb_memcache; Database changed mysql> SHOW TABLES; +---------------------------+ | Tables_in_innodb_memcache | +---------------------------+ | cache_policies | | config_options | | containers | +---------------------------+ ... InnoDB ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-security.html
The following section shows how to build, enable, and test an SASL-enabled daemon_memcached plugin. Caution Consult this section before deploying the daemon_memcached plugin on a production server, or even on a test server if the MySQL instance ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-troubleshoot.html
This section describes issues that you may encounter when using the InnoDB memcached plugin. If you encounter the following error in the MySQL error log, the server might fail to start: failed to set rlimit for open files. One solution is to raise ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-midpoint_insertion.html
To help you gauge the effect of setting these parameters, the SHOW ENGINE INNODB STATUS command reports buffer pool statistics. Rather than using a strict LRU algorithm, InnoDB uses a technique to minimize the amount of data that is brought into ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-multiple_io_threads.html
If you have a high end I/O subsystem and you see more than 64 × innodb_read_io_threads pending read requests in SHOW ENGINE INNODB STATUS output, you might improve performance by increasing the value of innodb_read_io_threads. InnoDB uses ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-read_ahead.html
The SHOW ENGINE INNODB STATUS command displays statistics to help you evaluate the effectiveness of the read-ahead algorithm. A read-ahead request is an I/O request to prefetch multiple pages in the buffer pool asynchronously, in anticipation that ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-ro-txn.html
Note Transactions that qualify as auto-commit, non-locking, and read-only (AC-NL-RO) are kept out of certain internal InnoDB data structures and are therefore not listed in SHOW ENGINE INNODB STATUS output. InnoDB can avoid the overhead associated ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-schema.html
Instance tables relevant to InnoDB include: The mutex_instances table The rwlock_instances table The cond_instances table The file_instances table Note Mutexes and RW-locks related to the InnoDB buffer pool are not included in this coverage; the ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-use_sys_malloc.html
Since InnoDB cannot track all memory use when the system memory allocator is used (innodb_use_sys_malloc is ON), the section “BUFFER POOL AND MEMORY” in the output of the SHOW ENGINE INNODB STATUS command only includes the buffer pool statistics ... When InnoDB was developed, the memory allocators supplied with operating systems and run-time libraries were often lacking in performance and ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-read-only-instance.html
As a consequence, SHOW ENGINE INNODB STATUS does not produce any output. You can query InnoDB tables where the MySQL data directory is on read-only media by enabling the --innodb-read-only configuration option at server startup. How to Enable To ...