Jonathan wrote:
"Of course, it'd be lovely if you could actually specify an upper memory
bound for a particular request to use, and/or Zope as a whole"
If your server is still alive and Zope is throwing memory errors, then
Zope has hit its specified upper memory limit.
No, Zope does little if anything to control the amount of memory it
uses. If it did, we wouldn't see MemoryErrors ;-)
What do you want Zope to
do at this point?
Start dumping objects out of the ZODB object cache when it reaches a
certain memory limit, preferably configurable in zope.conf.
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope maillist - [email protected]
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
