PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 295.2Kb
Man Pages (Zip)
- 400.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-cpudata-20sec.html
The cpudata_20sec table provides data about CPU usage per 20-second interval over the last 400 seconds.
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-cpudata-50ms.html
The cpudata_50ms table provides data about CPU usage per 50-millisecond interval over the last second.
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-cpudata.html
The cpudata table provides data about CPU usage during the last second.
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-transporter-details.html
sendbuffer_max_used_bytes The maximum amount, in bytes, of signal data awaiting send at any one time by this transporter. sendbuffer_max_alloc_bytes Maxmimum amount of send buffer, in bytes, allocated for signal data storage at any one time for this ... This table contains information about individual NDB transporters, rather than aggregate information as shown by the transporters ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-locks-per-fragment.html
This table also shows the total time spent waiting for locks successfully and unsuccessfully since fragment or table creation, or since the most recent restart. This is also true for the time values shown in the wait_ok_millis and wait_fail_millis ... The locks_per_fragment table provides information about counts of lock claim requests, and the outcomes of these requests on a per-fragment basis, serving as a companion table to operations_per_fragment and ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-shm-definition.html
For optimum performance, you can define a spin time for the SHM transporter (ShmSpinTime parameter); this affects both the data node receiver thread and the poll owner (receive thread or user thread) in NDB. ShmSpinTime Version (or later) NDB 8.0.13 ... Communications between NDB cluster nodes are normally handled using ...
https://dev.mysql.com/doc/refman/8.0/en/analyze-table.html
MySQL 8.0.31 and later also supports setting the histogram of a single column to a user-defined JSON value. This issue is resolved in MySQL 8.0.24 (and later), where ANALYZE TABLE no longer causes subsequent operations to wait. MySQL uses the stored ...ANALYZE [NO_WRITE_TO_BINLOG | LOCAL] TABLE tbl_name UPDATE HISTOGRAM ON col_name [, col_name] ...
https://dev.mysql.com/doc/refman/8.0/en/storage-engines.html
Storage engines are MySQL components that handle the SQL operations for different table types. (The CREATE TABLE statement in MySQL 8.0 creates InnoDB tables by default.) MySQL Server uses a pluggable storage engine architecture that enables ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-backup-concepts.html
A backup is a snapshot of the database at a given time. The data actually stored in the database tables at the time that the backup was made Transaction log. A sequential record telling how and when data was stored in the database Each of these ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-diskstat.html
The diskstat table provides information about writes to Disk Data tablespaces during the past 1 second.