Tres Seaver <tseaver@zope.com> wrote:
Pascal Peregrina wrote: | mmmm... I thought that thre was one cache per connection to Zeo ?? | | A standard Zope instance with Zeo has 4 connections to Zeo, and when you | look at the cache status, it is different for each connection (different | number of objects). | So I am not sure that there is anything shared accross connections.
There are two caches in play here: the in-memory cache is per-connection (and not specific to ZEO); the on-disk cache (which is ZEO-specific) is shared across connections.
| If I am right, then it makes no real difference to have many Zope with one | connection to Zeo vs. one Zope with many connections to Zeo. | | If I am wrong, then I agree, "it's a shame" :)
We would need to test to see if it ended up mattering. Cache behavior is almost *never* what I expect.
If ZEO cache became a problem, we could add a fake local ZEO server that caches and relays to the real ZEO server on a remote machine. Has anyone thought about or written such a beast ? Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg@nuxeo.com