1 |
I don't think this is what you think it is. I believe this is the size |
2 |
of all the records that will be transferred to other nodes in the |
3 |
cluser, not the total database size. When NDB Cluster first came into |
4 |
being, I was testing it with a 60GB database with 4xDell PE2600s with |
5 |
2GB of RAM. |
6 |
|
7 |
> -----Original Message----- |
8 |
> From: Kashani [mailto:kashani-list@××××××××.net] |
9 |
> Sent: Thursday, October 28, 2004 11:03 AM |
10 |
> To: gentoo-server@l.g.o |
11 |
> Subject: Re: [gentoo-server] MySQL-4.1 and <- Max |
12 |
> |
13 |
> |
14 |
> On Wed, 27 Oct 2004, Sancho2k.net Lists wrote: |
15 |
> |
16 |
> > Another thing - MySQL's new cluster'd server technology |
17 |
> (appropriately |
18 |
> > named MySQL Cluster) is available in the MySQL Max |
19 |
> distribution. (For |
20 |
> > those who don't know, Max is basically the same thing as |
21 |
> the standard |
22 |
> > MySQL server package, along with some not-quite-ready for |
23 |
> common use |
24 |
> > functionality like the BDB table handler and such.) Now, |
25 |
> MySQL-4.1.7 is |
26 |
> > available and the Max release has the Cluster components |
27 |
> packaged in; |
28 |
> > has anything like the Max thing ever been available in |
29 |
> Portage? It looks |
30 |
> > like the mysql ebuild is simply the standard Server |
31 |
> package. Having a |
32 |
> > Max package would be nice in order to get ahold of the |
33 |
> MySQL Cluster |
34 |
> > components. |
35 |
> |
36 |
> I was interested in their cluster product until I read |
37 |
> the fine print. Your clustered database has to fit entirely |
38 |
> into RAM on each machine in the cluster. While this is |
39 |
> actually useful for a number of things like authenticating |
40 |
> users, it's a major limitation if you want |
41 |
> general clustering and have databases larger than 2GB. |
42 |
> |
43 |
http://dev.mysql.com/doc/mysql/en/MySQL_Cluster_DB_Definition.html under |
44 |
|
45 |
DataMemory |
46 |
|
47 |
kashani |