RE: the memory required for cluster's ndbd nodes - Feng Xie (fxie) - com.mysql.lists.cluster

9 messages in com.mysql.lists.clusterRE: the memory required for cluster's...

From	Sent On	Attachments
Feng Xie (fxie)	27 Feb 2006 09:05
Jimmy Guerrero	27 Feb 2006 09:15
Walter Bertot	27 Feb 2006 09:20
Feng Xie (fxie)	27 Feb 2006 09:45
Walter Bertot	27 Feb 2006 09:53
Adam Dixon	27 Feb 2006 14:51
Feng Xie (fxie)	28 Feb 2006 13:59
Stewart Smith	28 Feb 2006 15:44
Hartmut Holzgraefe	28 Feb 2006 16:27

Subject:	RE: the memory required for cluster's ndbd nodes
From:	Feng Xie (fxie) (fx...@cisco.com)
Date:	02/27/2006 09:45:20 AM
List:	com.mysql.lists.cluster

Walter:

Thanks for your reply. However, it is still unclear to me.

My ultimate question is : if the RAM isn't enough on a NDBD node, will the node stop working completely OR it still runs with downgraded performance due to paging activities.

To me, it is more tolerable to run with downgraded performance as long as the database is still accessable.

Could you clarify on this ?

Thanks, Feng

-----Original Message----- From: Walter Bertot [mailto:walt...@gmail.com] Sent: Monday, February 27, 2006 12:21 PM To: clus...@lists.mysql.com Cc: Feng Xie (fxie) Subject: RE: the memory required for cluster's ndbd nodes

Your interpretation is correct. Presently on the GA release everything resides in RAM although some light disk based storage is to be released shortly.

Yes paging would kick in however I would not recommend it due to the significant performance hit.

-----Original Message----- From: Feng Xie (fxie) [mailto:fx...@cisco.com] Sent: Monday, February 27, 2006 12:06 PM To: clus...@lists.mysql.com Subject: the memory required for cluster's ndbd nodes

Hi,

From the reference manual of MySQL 5.0, it seems to me that all table records, index data and some other data( such as UNDO records) have to reside in RAM all the time. Is my own interpretation correct ?

I am wondering whether PAGING/SWAP would kick in if RAM is not enough (at the price of lower performance ). I am a little worried that if we have to keep up with ever bigger RAM along the ever increasing database.

Thanks, Feng