[Zope-DB] Taking advantage of MySQLs inbuilt chache

[Charlie Clark]

I'm returning this to the list so that everyone can benefit.

On 2004-03-03 at 11:20:25 [+0100], you wrote:
> Mainly because the memory use can build up due to my heavy use of sql. MySQL
> is fairly intelligent/efficient in expiring caches and on our Debian Linux
> box these Zope SQL caches do not appear to have their memory reclaimed when
> they expire - (though I can't definitively say that is where my leak is)
> meaning I have to restart Zope every week.

This is interesting and sounds like a bug. Which version of Zope are you 
running? Doesn't clearing the general Zope cache make a difference?
 
> It shouldn't need anything other than the standard SQL to take advantage of
> the cache as all it needs is a 2nd SELECT query that has exact same binary
> size of the 1st but for some reason the direct MySQL drivers don't seem to
> 'hit' the cache suggesting that even though the plain text SQL is the same
> the processed query is somehow a different binary size to MYSQL each time.

Interesting. I wonder if this is a standard mechanism for query optimisers.
 
> Maybe if I try the mxODBC drivers they might work :)

yeah, give them a try and let us know!
-- 
Charlie Clark
eGenix.com

Professional Python Services directly from the Source
 >>> Python/Zope Consulting and Support ...        http://www.egenix.com/
 >>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
 >>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________

::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::