Search



Search Results
Displaying 281 to 290 of 1830 total results
https://dev.mysql.com/doc/refman/8.4/en/myisamchk-other-options.html
(The first time you use this option to sort a table, it may be very slow.) To determine a table's index numbers, use SHOW INDEX, which displays a table's indexes in the same order that myisamchk sees them. myisamchk supports the following options ...
https://dev.mysql.com/doc/refman/8.4/en/myisamchk-table-info.html
This operation is slow because it must read the entire table. To obtain a description of a MyISAM table or statistics about it, use the commands shown here. The output from these commands is explained later in this section. myisamchk -d tbl_name ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-config-starting.html
The following config.ini file is a recommended starting point for configuring a cluster running NDB Cluster 8.4: # TCP PARAMETERS [tcp default] SendBufferMemory=2M ReceiveBufferMemory=2M # Increasing the sizes of these 2 buffers beyond the default ...Changes in configuration are also likely to be indicated when changes are made in the platform on which the cluster is run, or in applications that use the NDB Cluster 's ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-replication-issues.html
This section discusses known problems or issues when using replication with NDB Cluster. A loss of connection can occur either between the source cluster SQL node and the replica cluster SQL node, or between the source SQL node and the data nodes ...
https://dev.mysql.com/doc/refman/8.4/en/mysqlshow.html
The mysqlshow client can be used to quickly see which databases exist, their tables, or a table's columns or indexes. The same information can be obtained by using those statements directly. For example, you can issue them from the mysql client ...
https://dev.mysql.com/doc/refman/8.4/en/optimization.html
Optimizing CPU and memory usage can also improve scalability, allowing the database to handle more load without slowing down. This chapter explains how to optimize MySQL performance and provides examples. Depending on your job role (developer, DBA, ...
https://dev.mysql.com/doc/refman/8.4/en/optimizing-innodb-storage-layout.html
This operation can be slow if the table is large or if the indexes being rebuilt do not fit into the buffer pool. The first run after adding a lot of data to a table is often much slower than later runs. Once your data reaches a stable size, or a ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-concepts.html
If the server has a mix of InnoDB transactions and non-InnoDB transactions, which are written to the mysql.gtid_executed table individually, the compression carried out by the compress_gtid_table thread interferes with the work of the GTID persister ... A global transaction identifier (GTID) is a unique identifier created and associated with each transaction committed on the server of origin (the ...
https://dev.mysql.com/doc/refman/8.4/en/replication-options-gtids.html
If the server has a mix of InnoDB transactions and non-InnoDB transactions, the compression controlled by this system variable interferes with the work of this process and can slow it significantly. The MySQL Server system variables described in ...
https://dev.mysql.com/doc/refman/8.4/en/replication-semisync-interface.html
These settings help as the number of replicas increases, because contention for locks can slow down performance. When you install the source and replica plugins for semisynchronous replication (see Section 19.4.10.1, “Installing Semisynchronous ...
Displaying 281 to 290 of 1830 total results