MySQL :: MySQL 8.0 Reference Manual

Search Results

Displaying 51 to 60 of 61 total results

9.6.5 Setting Up a MyISAM Table Maintenance Schedule

https://dev.mysql.com/doc/refman/8.0/en/myisam-maintenance-schedule.html

To start with, execute myisamchk -s each night on all tables that have been updated during the last 24 hours. It is a good idea to perform table checks on a regular basis rather than waiting for problems to occur. One way to check and repair MyISAM ...

10.2.3 Optimizing INFORMATION_SCHEMA Queries

https://dev.mysql.com/doc/refman/8.0/en/information-schema-optimization.html

The default is 86400 seconds (24 hours), but the time period can be extended to as much as one year. Applications that monitor databases may make frequent use of INFORMATION_SCHEMA tables. To write queries for these tables most efficiently, use the ...

28.3.34 The INFORMATION_SCHEMA STATISTICS Table

https://dev.mysql.com/doc/refman/8.0/en/information-schema-statistics-table.html

The information_schema_stats_expiry system variable defines the period of time before cached table statistics expire. If there are no cached statistics or statistics have expired, statistics are retrieved from storage engines when querying table ...

28.3.38 The INFORMATION_SCHEMA TABLES Table

https://dev.mysql.com/doc/refman/8.0/en/information-schema-tables-table.html

17.1.2 Best Practices for InnoDB Tables

https://dev.mysql.com/doc/refman/8.0/en/innodb-best-practices.html

While you don't want to commit too often, you also don't want to issue huge batches of INSERT, UPDATE, or DELETE statements that run for hours without committing. Specify a primary key for every table using the most frequently queried column or ...

17.5.2 Change Buffer

https://dev.mysql.com/doc/refman/8.0/en/innodb-change-buffer.html

Change buffer merging may take several hours when there are many affected rows and numerous secondary indexes to update. The change buffer is a special data structure that caches changes to secondary index pages when those pages are not in the ...

17.15.1.1 INNODB_CMP and INNODB_CMP_RESET

https://dev.mysql.com/doc/refman/8.0/en/innodb-information-schema-innodb_cmp.html

For example, if you archive the output of INNODB_CMP_RESET every 60 minutes, you see the statistics for each hourly period. The INNODB_CMP and INNODB_CMP_RESET tables provide status information about operations related to compressed tables, which ...

17.15.1.2 INNODB_CMPMEM and INNODB_CMPMEM_RESET

https://dev.mysql.com/doc/refman/8.0/en/innodb-information-schema-innodb_cmpmem.html

For example, if every 60 minutes you archived the output of INNODB_CMPMEM_RESET, it would show the hourly statistics. The INNODB_CMPMEM and INNODB_CMPMEM_RESET tables provide status information about compressed pages that reside in the buffer pool.

17.8.1 InnoDB Startup Configuration

https://dev.mysql.com/doc/refman/8.0/en/innodb-init-startup-configuration.html

Generally, the combined size of the log files should be large enough that the server can smooth out peaks and troughs in workload activity, which often means that there is enough redo log space to handle more than an hour of write activity. The ...

17.12 InnoDB and Online DDL

https://dev.mysql.com/doc/refman/8.0/en/innodb-online-ddl.html

Benefits of this feature include: Improved responsiveness and availability in busy production environments, where making a table unavailable for minutes or hours is not practical. The online DDL feature provides support for instant and in-place ...

Displaying 51 to 60 of 61 total results