MySQL Forums
Forum List  »  Memory Storage Engine

engine=memory versus query_cache
Posted by: Bodo Fritsche
Date: March 30, 2006 11:46AM


I have a table that need never to be stored on disk (user online statistics) with a high degree of INSERT, UPDATE and DELETE, so it is a candidate for a memory table (myisam).

Also, I have other tables where the relationship between SELECTS and UPDATES is 5000:1 (myisam), so these are candidates for a global query_cache.

Am I right so far?

But: What does mysql do if both is specified?

Is the memory table also query cached which makes no sense because of the high update frequency of the memory table?

It would be too hard to alter the php code to distinguish between both behaviours.

Thanks for helping.


Edited 1 time(s). Last edit at 03/30/2006 03:49PM by Bodo Fritsche.

Options: ReplyQuote

Written By
engine=memory versus query_cache
March 30, 2006 11:46AM

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.