engine=memory versus query_cache
Hi,
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.
Bodo
Edited 1 time(s). Last edit at 03/30/2006 03:49PM by Bodo Fritsche.
Subject
Views
Written By
Posted
engine=memory versus query_cache
10798
March 30, 2006 11:46AM
5502
March 31, 2006 01:29AM
5091
March 31, 2006 02:27AM
5088
April 03, 2006 04:49AM
5444
April 04, 2006 03:12PM
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.