Man, I'm frustrated... while getting a client's project ready for deployment I noticed that performance on the production server was dismal and went about debugging when I realized that the CPU-hog wasn't the new project but... the Zope instance serving tomster.org...!

Its ZODB had grown to over 2.2Gb in size (eventhough the site doesn't contain more than ca. 300Mb actual data) and every click on it sent the CPU usage up to 100%. I decided to export the content and set up a new instance to alleviate the performance problem.

No dice! The attempt to export the plone instance to a .zexp causes the zope process to crash after ca. a minute. So does the attempt to compact the database. And... in the attempt to export each top-level folders of the site on its own so did the attempt to export my blog.

At the moment I don't have any time or energy to pursue the matter any further, as the aforementioned client project clearly takes prority.

At least now with the new instance the performance seems to be back to normal again...