Re: 3 different architectures - best perfromance and redudancy?

[Tarmo Loorits]

I yet have to finish my own testing but following my own logic, I would put my trust on setup2 where NDB and MySQL engine run on same node (server1/2). This is because NDB is mainly i/o-bound and probably does not use up much processor resources, while My-SQL is more CPU-bound, helping to utilize CPU-resources better. This also allows fast data transfer between MySQL and NDB in localhost instead of 100Mb Ethernet. And definitely it would be helpful to have 1Gb Etherenet crossover between two cluster nodes because there will be lot of traffic between NDB instances. There is lot less traffic between Apache and MySQL, so it is probably fine over 100Mb Ethernet and it can probably benefit of dual processors better then anything else.