Search Results
https://dev.mysql.com/doc/refman/8.4/en/myisamchk-memory.html
myisamchk uses no more memory than its memory-related variables are set to. If you are going to use myisamchk on very large tables, you should first decide how much memory you want it to use. The default is to use only about 3MB to perform repairs.
https://dev.mysql.com/doc/refman/8.4/en/myisampack.html
When the table is used later, the server reads into memory the information needed to decompress columns. This results in much better performance when accessing individual rows, because you only have to uncompress exactly one row. MySQL uses mmap() ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-calendar.html
MySQL uses what is known as a proleptic Gregorian calendar. Every country that has switched from the Julian to the Gregorian calendar has had to discard at least ten days during the switch. To see how this works, consider the month of October 1582, ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-computer-definition.html
The [computer] section has no real significance other than serving as a way to avoid the need of defining host names for each node in the system. Id Version (or later) NDB 8.4.0 Type or units string Default [...] Range ... Restart Type Initial ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-install-windows-service.html
Once you are satisfied that NDB Cluster is running as desired, you can install the management nodes and data nodes as Windows services, so that these processes are started and stopped automatically whenever Windows is started or stopped. This also ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-interconnects.html
Even before design of NDBCLUSTER began in 1996, it was evident that one of the major problems to be encountered in building parallel databases would be communication between the nodes in the network. For this reason, NDBCLUSTER was designed from ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-limitations-database-objects.html
Some database objects such as tables and indexes have different limitations when using the NDBCLUSTER storage engine: Number of database objects. The maximum number of all NDB database objects in a single NDB Cluster—including databases, tables, ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-limitations-disk-data.html
Disk data objects are subject to the following maximums and minimums: Maximum number of tablespaces: 232 (4294967296) Maximum number of data files per tablespace: 216 (65536) The minimum and maximum possible sizes of extents for tablespace data ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-limitations-exclusive-to-cluster.html
The following are limitations specific to the NDB storage engine: Machine architecture. All machines used in the cluster must have the same architecture. That is, all machines hosting nodes must be either big-endian or little-endian, and you cannot ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-limitations-performance.html
The following performance issues are specific to or especially pronounced in NDB Cluster: Range scans. There are query performance issues due to sequential access to the NDB storage engine; it is also relatively more expensive to do many range ...