-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 25 Feb 2007, at 21:19, Maciej Wisniowski wrote:
Caching will not make any difference to memory behavior I'd say. I'm not expert here, so I might be wrong but AFAIK Zope instance loads 'touched' objects from ZODB into cache. Each ZODB connection has its own cache, so having object touched more than once may cause it is loaded to more than one cache.
The same will possibly be with multiple ZEO clients. External cache will save them from being touched (sometimes even once).
ZODB connections cache is cleaned sometimes, so it should flush objects that are old and possibly save some memory then.
I don't know whether amount of memory used because of above is huge enough to cause described problem. It's just a though.
This is a bit like clutching at straws. You're doctoring the symptoms, hoping that some things may not be loaded into memory. It's not a real solution. Memory-hungry applications will remain memory- hungry, cached or not. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFF4gWoRAx5nvEhZLIRAoGbAJ9U0DMyhO6JA3A8HCAcTkrbpjzq/QCfTxGk wrad3smxlEaFKUXNNacUzio= =Ef9a -----END PGP SIGNATURE-----