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.
--Paul
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
and
Michael Bernstein wrote:
Michael Bernstein wrote:
I figured out how to get this to work (finally).
In the acl_users LM, add the following two Python methods:
Well, I discovered another problem:
For some reason, when I create a PortalMembership member, add the two
Python methods
