Re: SQL Cluster Performane worse than MyISAM.

[Arié TIBI]

Hi Andrew,

I am quite all right with you about poor performances of cluster mysql. You can see my article and results "Bad performance mysql cluster versus innodb". Every basic operation is 5 times slower (and high resource consumption) with NDBCLUSTER (Full table scan, insert, delete, ....)

In another hand, about Innodb, you can tune a lot of memory parameters and you get near the same results than MyIsam(see my article). The advantage of InnoDb is that is more secure than Myisam (no more frequent "repair table")

Here is another test with "vmstat 1" about NDBCLUSTER / Innodb :

This script inserts 10000 lines:
==================

truncate table ctest:
insert into ctest3 values('1');
...
insert into ctest3 values('10000');

If ctest is NDBCLUSTER :
================
procs memory swap io system cpu
r b swpd free buff cache si so bi bo in cs us sy id wa
1 0 31220 6448 91880 183392 0 0 0 0 108 687 0 1 99 0
1 1 31220 6444 91888 183124 0 0 0 144 117 1239 25 5 70 0
2 0 31220 6364 91908 183104 0 0 0 36 116 2478 77 19 4 0
1 0 31220 6496 91908 182872 0 0 0 0 109 13773 59 41 0 0
1 0 31220 6572 91932 182836 0 0 0 944 135 13245 61 39 0 0
1 0 31220 6524 91960 182856 0 0 0 220 118 13446 60 38 2 0
1 0 31220 6524 91980 182832 0 0 0 424 126 14168 48 52 0 0
1 0 31220 6448 91988 182856 0 0 0 16 109 14263 58 42 0 0
1 0 31220 6408 91988 182888 0 0 0 0 107 14294 57 43 0 0
1 0 31220 6516 92016 182792 0 0 0 368 127 13998 64 34 0 2
1 0 31220 6492 92024 182824 0 0 0 188 116 14244 53 47 0 0
2 0 31220 6496 92024 182820 0 0 0 0 107 13938 57 41 2 0
1 0 31220 6464 92048 182828 0 0 0 432 129 14243 59 41 0 0
3 0 31220 6428 92048 182860 0 0 0 0 108 10925 60 40 0 0
1 0 31220 6472 92072 182792 0 0 0 404 123 6985 55 43 2 0
1 0 31220 6476 92140 182620 0 0 8 704 151 7044 57 43 0 0
1 1 31220 6532 92180 182528 0 0 8 392 130 7012 56 44 0 0
1 1 31220 8980 92236 179884 116 0 120 3952 181 6135 53 40 0 7
1 1 31220 6532 92268 182244 0 0 0 2836 240 6401 65 33 0 2
2 0 31220 6360 92324 182416 0 0 4 860 161 7064 52 48 0 0
1 0 31220 6280 92364 182456 0 0 0 408 139 7023 68 30 2 0
1 0 31220 6408 92364 182232 0 0 0 0 106 7061 58 42 0 0
1 0 31220 6504 92388 182204 0 0 0 436 123 7025 55 45 0 0
1 0 31220 6576 92388 182224 0 0 0 0 109 4526 38 22 40 0
1 0 31220 6548 92416 182292 0 0 0 296 123 775 1 0 96 3

If ctest is InnoDB :
============
procs memory swap io system cpu
r b swpd free buff cache si so bi bo in cs us sy id wa
1 0 30964 6416 92444 182524 0 0 0 180 127 794 1 0 97 2
1 0 30964 6484 92444 182456 0 0 0 0 112 448 54 0 46 0
2 0 30964 6560 92200 182620 0 0 4 640 118 2295 82 11 0 7
1 0 30964 6532 92228 182684 0 0 4 384 126 6196 78 18 0 4
1 0 30964 6532 91996 182916 0 0 4 328 124 7923 67 25 0 9
1 0 30964 6500 91996 182932 0 0 4 144 118 8348 74 24 0 3
2 0 30964 6504 91736 183204 0 0 4 140 114 8503 74 25 0 2
1 0 30964 6512 91736 183384 0 0 4 116 113 4569 37 12 49 2
2 0 30964 6504 91504 183624 0 0 0 772 134 790 1 0 89 10

I don't understand what a lot of things is writing Mysql cluster (column "bo")

I thing tuning parameters must exist (I already tryed certain of them : memory, tcp ip) but they are not still diffused.

Regards