Chris Withers wrote:
However, I just checked the cache manger stats page today and I'm getting 25 misses per hit, not very good at all :-( To boot, there are 193 entries in the cache for a method that doesn't change, and they're taking up 350kb of RAM for no good reason.
Did you define a non-empty set of request variables? If so its entirely possibly thats why there are different entries for the same method. Is the method a page template? RAM Cache Managers are lousy at caching page templates because page templates store data in their keywords which can change as the memory usage of your zope process changes and python re-orders things. Finally, remember that 350k is an aproximation garnered by the pickle size of the cached content, its not an exact reflection of the actual memory consumption, its only ment as a rough guide.
Is this likely to be a bug in 2.6.2b4 or could I haev tweaked something to get these kind of bad results?
Its probably just reflective of some of the design choices behind RAM Cache Manager. I wrote a diatribe on caching 2 months ago, check it: http://marc.theaimsgroup.com/?l=zope&m=105460381811223&w=2 -- Jamie Heilman http://audible.transient.net/~jamie/ "We must be born with an intuition of mortality. Before we know the words for it, before we know there are words, out we come bloodied and squalling with the knowledge that for all the compasses in the world, there's only one direction, and time is its only measure." -Rosencrantz