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/innodb-memcached-replication.html
It is assumed that you have completed the setup described in Section 17.20.3, “Setting Up the InnoDB memcached Plugin”. Because the daemon_memcached plugin supports the MySQL binary log, source server through the memcached interface can be ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-setup.html
The table must have a key column with a unique index. This section describes how to set up the daemon_memcached plugin on a MySQL server. Because the memcached daemon is tightly integrated with the MySQL server to avoid network traffic and minimize ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-tuning.html
Because of the way InnoDB organizes memcached key values on disk, if you have a large number of keys to create, it may be faster to sort the data items by key value in the application and add them in sorted order, rather than create keys in ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-online-ddl-single-multi.html
If the specific changes were different each time, you might have to construct a new complex ALTER TABLE for each slightly different scenario. Before the introduction of online DDL, it was common practice to combine many DDL operations into a single ...
https://dev.mysql.com/doc/refman/8.0/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/8.0/en/innodb-performance-read_ahead.html
For example, if you set the value to 48, InnoDB triggers a linear read-ahead request only when 48 pages in the current extent have been accessed sequentially. A read-ahead request is an I/O request to prefetch multiple pages in the buffer pool ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-performance-ro-txn.html
The transaction is started without the READ ONLY option, but no updates or statements that explicitly lock rows have been executed yet. InnoDB can avoid the overhead associated with setting up the transaction ID (TRX_ID field) for transactions that ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-performance-spin_lock_polling.html
That time equivalence did not hold, but PAUSE instruction duration remained fairly constant in terms of processor cycles relative to other CPU instructions until the introduction of the Skylake generation of processors, which have a comparatively ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-redo-log-buffer.html
Thus, if you have transactions that update, insert, or delete many rows, increasing the size of the log buffer saves disk I/O. The log buffer is the memory area that holds data to be written to the log files on disk. The contents of the log buffer ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-redo-log.html
The MySQL user running the backup utility or the MySQL user activating and deactivating redo log archiving manually must have this privilege. The redo log is a disk-based data structure used during crash recovery to correct data written by ...