Hedley Roos wrote:
> Since memcached is distributed only a single Zope client needs to
> perform that query and the result is available to all other Zope
> clients. 

This is where you'll get the big win: no need to load all the 
catalog-related objects into the zodb cache on all the clients which has 
the twin drawbacks of needing to be done and trashing your zodb cache...

> And the cache is "persistent" as long as memcached runs, so
> you can merrily restart Zope instances and have a warm cache. I didn't
> even realise this until Roche pointed it out to me.

Coool :-)



Simplistix - Content Management, Zope & Python Consulting
            - http://www.simplistix.co.uk
Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to