PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.3Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/table-scan-avoidance.html
Start mysqld with the --max-seeks-for-key=1000 option or use SET max_seeks_for_key=1000 to tell the optimizer to assume that no key scan causes more than 1,000 key seeks. This usually happens under the following conditions: The table is so small ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-innodb-buffer-page-lru-table.html
The INNODB_BUFFER_PAGE_LRU table provides information about the pages in the InnoDB buffer pool; in particular, how they are ordered in the LRU list that determines which pages to evict from the buffer pool when it becomes full. For related usage ...The INNODB_BUFFER_PAGE_LRU table has the same columns as the INNODB_BUFFER_PAGE table, except that the INNODB_BUFFER_PAGE_LRU table has LRU_POSITION and COMPRESSED columns instead of BLOCK_ID and PAGE_STATE ...
https://dev.mysql.com/doc/refman/5.7/en/keyring-functions-plugin-specific.html
For each keyring plugin-specific function, this section describes its purpose, calling sequence, and return value. For information about general-purpose keyring functions, see Section 6.4.4.8, “General-Purpose Keyring Key-Management Functions”.
https://dev.mysql.com/doc/refman/5.7/en/optimizing-spatial-analysis.html
For MyISAM and InnoDB tables, search operations in columns containing spatial data can be optimized using SPATIAL indexes. The most typical operations are: Point queries that search for all objects that contain a given point Region queries that ...
https://dev.mysql.com/doc/refman/5.7/en/sys-io-global-by-file-by-latency.html
These views summarize global I/O consumers to display time waiting for I/O, grouped by file. total_latency The total wait time of timed I/O events for the file. count_read The total number of read I/O events for the file. read_latency The total ...
https://dev.mysql.com/doc/refman/5.7/en/mysqld-server.html
This setting modifies certain aspects of SQL syntax and semantics, for example for compatibility with code from other database systems, or to control the error handling for particular situations. There are performance and reliability considerations ...The following discussion covers these MySQL server configuration topics: Startup options that the server ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-index-types.html
To get the best performance from queries, inserts, and other database operations, it is important to understand how InnoDB uses the clustered index to optimize the common lookup and DML operations. If there is no logical unique and non-null column ... Each InnoDB table has a special index called the clustered index that stores row ...
https://dev.mysql.com/doc/refman/5.7/en/federated-description.html
If the statement produces a result set, each column is converted to internal storage engine format that the FEDERATED engine expects and can use to display the result to the client that issued the original statement. A FEDERATED table consists of ...
https://dev.mysql.com/doc/refman/5.7/en/optimize-blob.html
Since the performance requirements to retrieve and display a BLOB value might be very different from other data types, you could put the BLOB-specific table on a different storage device or even a separate database instance. For a table with several ... When storing a large blob containing textual data, consider compressing it ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-examples.html
Tune a query by writing it differently, Tune the database schema (tables, indexes, and so forth). The Performance Schema is a tool to help a DBA do performance tuning by taking real measurements instead of “wild guesses.” This section ...Then ...