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/performance-schema-host-cache-table.html
The MySQL server maintains an in-memory host cache that contains client host name and IP address information and is used to avoid Domain Name System (DNS) lookups. The host_cache_size system variable controls the size of the host cache, as well as ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-hosts-table.html
The hosts table contains a row for each host from which clients have connected to the MySQL server. For each host name, the table counts the current and total number of connections. To set the table size explicitly, set the ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-performance-timers-table.html
For an explanation of how event timing occurs, see Section 29.4.1, “Performance Schema Event Timing”. For a cycle timer, the frequency is generally related to the CPU speed. For example, on a system with a 2.4GHz processor, the CYCLE may be ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-pre-filtering.html
Pre-filtering is done by the Performance Schema and has a global effect that applies to all users. Pre-filtering can be applied to either the producer or consumer stage of event processing: To configure pre-filtering at the producer stage, several ...
https://dev.mysql.com/doc/refman/8.0/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 ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-replication-applier-status-by-worker-table.html
This table provides details of the transactions handled by applier threads on a replica or Group Replication group member. For a single-threaded replica, data is shown for the replica's single applier thread. For a multithreaded replica, data is ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-replication-applier-status-table.html
This table shows the current general transaction execution status on the replica. The table provides information about general aspects of transaction applier status that are not specific to any thread involved. Thread-specific status information is ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-restrictions.html
The Performance Schema avoids using mutexes to collect or produce data, so there are no guarantees of consistency and results can sometimes be incorrect. If you save event information in another table, you should not assume that the original events ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-rwlock-instances-table.html
The rwlock_instances table lists all the rwlock (read write lock) instances seen by the Performance Schema while the server executes. An rwlock is a synchronization mechanism used in the code to enforce that threads at a given time can have access ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-statement-digests.html
The MySQL server is capable of maintaining statement digest information. The digesting process converts each SQL statement to normalized form (the statement digest) and computes a SHA-256 hash value (the digest hash value) from the normalized ...