On Dec 6, 2004, at 3:51 PM, Harrison Fisk wrote:
Hi,
On Monday, December 6, 2004, at 04:15 PM, Klaus Berkling wrote:
I beginning to use MySQL clustering abilities for a large records keeping solution.
I have installed 4.1.7 with the clustering components. The ndbd and ndb_mgmd processes are running. I can create the database and tables using the ndb engine.
I have started to import our data. I gather from the manual that tables are stored in RAM. I am trying to import a database with 11 tables with about 7 million rows. If I follow the math in the manual, one row will use 32KB, I would need 224 TB of RAM.
[...] 12.6MB + (460 + 16)*7,000,000 = ~3.3G data * NoOfReplicas
So you can see it isn't much more than your regular tables. If you had the actual table schema it could be a much closer estimate.
Thanks, this helps.
[...]
Also keep in mind it will be split across all of the machines in the cluster so even if you need 15 gigs of ram, you could do it with 4 * 4GB machines.
What happens if a node goes down?
kib
smime.p7s
Description: S/MIME cryptographic signature