Well, I noticed what was the culprit. It turned out that portal_catalog turned into a 'tumor'. When I export the catalog it results in a 195Mb file while a few days earlier it was only a few Mbs. For some reason it suddenly grew many times larger than all my content together while hardly any new content was added. Reindexing took ages. About 1000+x longer than normal (= 70seconds). Now it took almost an hour to reindex my content. So then I decided to tried I cleared all indexes. I then tried to let it recreate the indexes (Find tab) but that took ages too. In fact it never finished (I stopped it eventually). So that didn't work. Then I got a backup from a few days old. I exported all my content from the tumorous database and imported it into the backup version (after first removing the existing content). Then I let it reindex the portal_catalog in the backup version and then things were back to normal again. It took about 70seconds to reindex and the database was about 45Mb. I have no idea why the catalog suddenly got into this state and why it took about 2 minutes to save plone content (reindexing the object) and why it took one hour for a full reindex. Right now my database is ok again but this really freaks me out!!! At that point I realized again how much of a black box the zope database actually is and I really keep my fingers crossed that nothing more serious will happen. Danny "Dieter Maurer" <dieter@handshake.de> wrote in message news:16546.35043.313060.656109@gargle.gargle.HOWL...
Danny Bloemendaal wrote at 2004-5-11 17:08 +0200:
I have a production zope database with a size of 225Mb (after pack) and a local database (identical environment) which is a copy of production that is a few days old with a size of 45Mb. In a desperate attempt to find out where all these hundreds of Mb came from in only a few days while not much was added in the production database I did some tests:
Recently, someone had a problem similar to yours. He posted results he had derived with an "analyse.py" script.
I do not know what "analyse.py" is and who is his author. But, the information derived by it was *very* useful to get clues towards the problem cause.
Maybe, you use a search engine to locate the relevant thread and contact the poster for information about "analyse.py".
-- Dieter
_______________________________________________ Zope maillist - Zope@zope.org 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 )