Andy McKay wrote:
>
> We have been looking at caching in Zope as a way of tweaking performance.
> Heres an example of what I think happens:
>
> - Supposing I have a 1,000 object catalog. If one person changes an catalog
> aware object, that instance of the catalog will be pulled out of the ZODB
Andy McKay wrote:
> > What problem are you trying to solve -- response time, memory usage,
> > disk usage?
>
> All of the above :)
Describe some of the symptoms back on the list and let's talk about it
there. For instance, you can trade RAM for performance by adjusting
knobs on the catalog.
--
Statement of possible BS: I am speaking from how I understand the
catalog
to work, and possibly not how it actually *does* work. :-)
Andy McKay wrote:
>
> We have been looking at caching in Zope as a way of tweaking performance.
> Heres an example of what I think happens:
>
> - Supposing I have
Thanks
> (I'm only talking about text indices here.)
>
> Note that the Catalog is actually a tree of database/cache objects.
> There are a series of buckets and sub-buckets that end in a word
> object. The buckets, sub-buckets, and words are all database objects
> and can be cached/updated se
