Subtransactions did the trick. I set the subtransaction size rather small (100 records before commit), it did take quite a long time. However it seems to be working now, I've got all the records in there. The machine is fairly hefty, Athlon XP 2Ghz, with 1GB RAM. Is there any way to time how long a transaction takes to get comitted? I noticed that when the script finished executing, the catalog hadn't comitted the transactions yet (despite subtransactions being enabled - or at least I thought they were). It wasn't until I checked again hours later that I noticed the # of items in the catalog had been increased. -jim -----Original Message----- From: Chris Withers [mailto:chris@simplistix.co.uk] Sent: Thursday, July 22, 2004 5:00 AM To: Roché Compaan Cc: Jim Kutter; zope@zope.org Subject: Re: [Zope] Force a ZODB transaction commit? Roché Compaan wrote:
I am sure that the catalog is not the culprit here - I regularly index 300k objects in one go. Your instance freezing could be due to memory consumption, committing a transaction every n records will help keep that in check.
ZCatalog does this by default with subtransactions. I'd look at the script doing the indexing, along with how much RAM the server has... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk 271 North Avenue Suite 1210 New Rochelle, NY 10801 ebizQ Links Webinars http://www.ebizq.net/webinars/?campaign=exchange White Papers http://www.ebizq.net/white_papers/?campaign=exchange