Alex Rice <alrice@swcp.com> writes:

On 26 Jun 1999 15:20:57 -0400, michel@digicool.com said:

michel> The several MB of text would probably translate into 2 or 3 michel> times that in memory growth. However, the Persistence machinery michel> will quickly start to deactivate unused portions of the index. michel> Try tweaking your Cache settings to see if you can get Zope to michel> be more aggresive about deactivating objects.

OK, here's some more data points, just in case it's useful:

My z2.py process starts at about 5-6MB memory usage. After indexing about 2MB of text, it goes up to 40 MB memory usage. Manually running the GC, it goes down to 38MB. (manage_pack and manage_cache_size are not implemented, yet, I think) Stopping, then starting Zope it goes back down to 5-6MB. After searching via the catalog it's at about 8MB and stays right around there.

Ok, this is pretty unusual, good clue that it only grows your process size by 2MB after a restart, I suspect then that there is some leak in the 'find and catalog' code.

Thanks for ZCatalog. It's going to be immensely useful.

Yes, it fills an aching gap in Zope's Open Source capabilities. -Michel

Alex Rice | alrice@swcp.com | http://www.swcp.com/~alrice Current Location: N. Rio Grande Bioregion, Southwestern USA

_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope

(For developer-specific issues, use the companion list, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )