MySQL Forums
Forum List  »  Memory Storage Engine

General q'stions about indexing and performance of MEMORY tables
Posted by: Julien Walther
Date: March 13, 2006 02:08AM


I'd like to seek some advice here concercing a consideration of a major design change of our db architecture. We have a fairly high-load website, the backend currently running on one master and three slaves.

Many large tables that are frequently written and read are InnoDB at the moment. As never all of the data is needed, we were considering to de-normalize and copy the relevant records that are needed to a MEMORY table once a day, which is then being queried by the users.

Will it be a significant performance increase of holding all vital data in a MEMORY table? (As InnoDB holds many data in memory anyways.) The new MEMORY table would then occupy only about 200 MB in memory, compared to 4 gigs on the disk now.

I have read some issues about the use of indexes with MEMORY tables. As the "new" MEMORY table would have many indexes and rely heavily on being queried with combined WHERE statements and sorting, I'd like to know if there is anything to consider.

Thank you in advance for your advices.


Edited 1 time(s). Last edit at 03/13/2006 02:08AM by Julien Walther.

Options: ReplyQuote

Written By
General q'stions about indexing and performance of MEMORY tables
March 13, 2006 02:08AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.