The following performance issues are specific to or especially pronounced in MySQL 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 scans than
it is with either MyISAM or
InnoDB.
Reliability of Records in range.
The Records in range statistic is
available but is not completely tested or officially
supported. This may result in non-optimal query plans in
some cases. If necessary, you can employ USE
INDEX or FORCE INDEX to alter
the execution plan. See Section 12.2.7.2, “Index Hint Syntax”, for
more information on how to do this.
Unique hash indexes.
Unique hash indexes created with USING
HASH cannot be used for accessing a table if
NULL is given as part of the key.

User Comments
Add your own comment.