just did some benchmarking on multi-threaded ndbd (binary called ndbmtd)
that is in the coming 6.4 release.
quite happy with results
[jonas@n1 run]$ flexAsynch -ndbrecord -temp -t 8 -p 512 -r 5 -a 2
insert average: 374200/s min: 374200/s max: 374200/s stddev: 0%
update average: 370947/s min: 370947/s max: 370947/s stddev: 0%
delete average: 395061/s min: 395061/s max: 395061/s stddev: 0%
read average: 537178/s min: 531948/s max: 543092/s stddev: 0%
this flexAsynch command will run with
- 8 threads
- 512 parallel transactions per thread
- 8 byte records.
note: during the reads, the datanode was *not* maxed out.
this was run on two identical computers,
2-socket, 4 cores per socket Intel(R) Xeon(R) CPU X5355 @ 2.66GHz
api-program was running on computer 1 (n1)
datanode was running on computer 2 (n2)
Quickly tell who is writing to a MySQL replica - Many of us have been there in the past, you get an alert telling you that replication has stopped because of an error, you dig in to it to find that you’re...
2 hours ago