PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.3Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/optimize-overview.html
Database performance depends on several factors at the database level, such as tables, queries, and configuration settings. These software constructs result in CPU and I/O operations at the hardware level, which you must minimize and make as ...
https://dev.mysql.com/doc/refman/5.7/en/optimizing-innodb-bulk-data-loading.html
These performance tips supplement the general guidelines for fast inserts in Section 8.2.4.1, “Optimizing INSERT Statements”. When importing data into InnoDB, turn off autocommit mode, because it performs a log flush to disk for every insert.
https://dev.mysql.com/doc/refman/5.7/en/optimizing-innodb-storage-layout.html
Once your data reaches a stable size, or a growing table has increased by tens or some hundreds of megabytes, consider using the OPTIMIZE TABLE statement to reorganize the table and compact any wasted space. The reorganized tables require less disk ...
https://dev.mysql.com/doc/refman/5.7/en/out-of-range-and-overflow.html
If no restrictive modes are enabled, MySQL clips the value to the appropriate endpoint of the column data type range and stores the resulting value instead. When an out-of-range value is assigned to an integer column, MySQL stores the value ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-limitations-functions.html
This section discusses limitations in MySQL Partitioning relating specifically to functions used in partitioning expressions. Each of these functions returns an integer only if it is passed an argument of an exact numeric type, such as one of the ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-consumer-configurations.html
The consumer settings in the setup_consumers table form a hierarchy from higher levels to lower. The following discussion describes how consumers work, showing specific configurations and their effects as consumer settings are enabled progressively ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-events-transactions-current-table.html
The table stores one row per thread showing the current status of the thread's most recent monitored transaction event, so there is no system variable for configuring the table size. For example: mysql> SELECT * FROM ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-file-instances-table.html
The file_instances table lists all the files seen by the Performance Schema when executing file I/O instrumentation. If a file on disk has never been opened, it is not in file_instances. When a file is deleted from the disk, it is also removed from ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-filtering.html
Events are processed in a producer/consumer fashion: Instrumented code is the source for events and produces events to be collected. The setup_instruments table lists the instruments for which events can be collected, whether they are enabled, and ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-queries.html
Pre-filtering limits which event information is collected and is independent of any particular user. By contrast, post-filtering is performed by individual users through the use of queries with appropriate WHERE clauses that restrict what event ...