I was recently involved in a project where the main requirement
was the smallest possible latency for queries. The queries were
simple insert and update statements, the update being by primary
key. The cluster was using regular Gigabits Ethernet and formed
by 3 servers with 8 cores each, one Management node and 2 data
nodes. Since throughput was not a concern, a design decision has
been made to locate the MySQL daemons on the same servers as the
data nodes, in order to save network hops. MySQL chooses the
closest NDB data node as its transaction coordinators and the
closest on will be reachable on localhost.
Apart from the architectural decision to host MySQL and the NDB
nodes on the same boxes, we decided to benchmark the new real
time options of NDB. The options are the following:
RealtimeScheduler: enable the real time schedule, was
set to 1
LockExecuteThreadToCPU: assign a given CPU to the
NDB execute thread, was set to 7, a …
[Read more]