On Friday 07 February 2003 1:48 am, george donnelly wrote:
Try these options:
1. pack the ZODB regularly (lessens your undo options)
That wont significantly reduce memory usage unless you havent packed for a very long time. The 'Cache Parameters' page has a 'Total number of objects in the database' field. Under filestorage you can expect to reclaim a few tens of bytes for each object romoved from this total by packing.
2. minimize the cache regularly (may use slightly more proc time)
In 2.6 the cache management is most efficient if you let it manage itself, by setting a realistic target size.
3. restart zope regularly (occasional brief (60-120 seconds) downtime as Zope and ZEO restart)
Yes, If you have a memoy leak
4. keep as many images and files out of the ZODB as possible (some inconvenience)
If this makes a significant difference then there is a bug. File and Image classes have optimisations because they expect to deal with large things. You will see a memory impact of other large (multi-megabyte) responese, such as from a DTML method 6. If you mave many concurrent users then use a front end proxy. 7. Set a smaller cache target size 8. Use fewer (2) threads. Memory usage is proportional to thread count. 9. Fix your memory leak. -- Toby Dickenson http://www.geminidataloggers.com/people/tdickenson