Re: Query Cache and simultaneous execution
Posted by:
Jay Pipes
Date: November 17, 2005 05:19PM
Like I said, if an explicit LOCK TABLES is issued, then the second thread should wait until a cached version is available. Other options would be to pre-populate the cache upon startup (using LOCK TABLES, then running SQL statements which would throw results into cache), using MEMORY tables which get pre-populated on startup and ensuring you issue a SQL_NO_CACHE keyword on those queries you know have extremely volatile result sets.
Jay Pipes
Community Relations Manager, North America, MySQL Inc.
Got Cluster?
http://www.mysql.com/cluster
Personal:
http://jpipes.com
Subject
Views
Written By
Posted
4029
November 15, 2005 05:43PM
1475
November 17, 2005 09:35AM
1542
November 17, 2005 10:40AM
1615
November 17, 2005 04:27PM
Re: Query Cache and simultaneous execution
1579
November 17, 2005 05:19PM
1469
November 17, 2005 05:46PM
1516
November 17, 2005 07:13PM
1427
February 04, 2006 08:48PM
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.