[ZODB-Dev] ZEO client leaking memory?

[sean.upton@uniontrib.com]

A week or two ago, Zope was using about 1200MB on each of my 2 load-balanced
ZEO client nodes, and each box, which has 512MB and about 1GB of swap was
unable to fork new processes.  Well, the site is a relatively high traffic
site, and I do three intensive tasks automated daily in the middle of the
night: first I add a few thousand objects to a bunch of folders containing
an aggregate of about 10-15k objects.  I then do a bulk ZCatalog reindex,
then I pack anything older than 1 day.  I've added to this mix a cron job to
restart Zope on both my nodes after all this is done, which has seemed to
solve my problem for now, but I'm still interested in finding out what sort
of problem I'm actually having.

Sean

-----Original Message-----
From: Toby Dickenson [mailto:tdickenson@devmail.geminidataloggers.co.uk]
Sent: Friday, October 05, 2001 2:40 AM
To: sean.upton@uniontrib.com
Cc: jeremy@zope.com; chrisw@nipltd.com; zodb-dev@zope.org
Subject: Re: [ZODB-Dev] ZEO client leaking memory?


On Thu, 04 Oct 2001 10:42:03 -0700, sean.upton@uniontrib.com wrote:

>Hmm... I have a similar problem, but I always assumed it was just a Catalog
>BTree memory leak issue, not a ZEO issue.

How much memory are you leaking?

The stress-test I was using to test memory pressure included 10k
indexing operations. adding roughly 500k ZODB objects in 5k documents.
If there was any leakage at all in the ZEO client, it was at most a
few megabytes. In the ZEO server leakage is difficult to distinguish
from FileStorage bloat, but it was at most a few tens of megabytes.
Thats quite a bit smaller than the problems Chris described.



Toby Dickenson
tdickenson@geminidataloggers.com