The following performance issues are specific to or especially pronounced in MySQL Cluster:
There are query performance issues due to sequential
access to the
engine; it is also relatively more expensive to do many
range scans than it is with either
Query cache. The query cache is disabled, since it is not invalidated if an update occurs on a different MySQL server.
Records in range.
Records in range statistic is
available but is not completely tested or officially
supported. This may result in nonoptimal query plans in
some cases. If necessary, you can employ
FORCE INDEX to alter
the execution plan. See Section 188.8.131.52, “Index Hint Syntax”, for
more information on how to do this.
Unique hash indexes.
Unique hash indexes created with
HASH cannot be used for accessing a table if
NULL is given as part of the key.