[Zope] Zope memory usage out of control

Chris McDonough chrism@digicool.com
Mon, 5 Feb 2001 20:51:34 -0500


It sounds like a potential memory leak.  These can be hard to track down...
any 3rd party product (or anything in the Zope core) can potentially leak.
Using the debug screen of the control panel can show you reference counts,
which can help a lot in determining what kinds of objects have the highest
reference count.  Using the auto-refresh (or periodic visits to the
"Refresh" link )on the debug screen when the site is in normal operation can
show you which kinds of objects are having a high "referred to" delta
between snapshots, which can maybe help us track down any leaks that may be
occurring.  This is probably the place to start.  Listing all of your
Products might help determine where the leak might be too.

----- Original Message -----
From: "Navindra Umanee" <navindra@cs.mcgill.ca>
To: <chrism@digicool.com>; <zope@zope.org>
Sent: Monday, February 05, 2001 8:16 PM
Subject: Re: [Zope] Zope memory usage out of control


>
> > > Please tell me that's really a single process with several threads all
> > > sharing memory? :-)
> >
> > Yes.  ;-)
>
> Phew.  ;)
>
> > > dot.kde.org is certainly a very busy site, is this the kind of memory
> > > usage to be expected from Zope?  Has anyone seen this kind of problem
> > > before?
> >
> > Does the memory usage grow without bound?  Or does it stay steady at a
large
> > amount? (Or have you not had the opportunity to find out?)
>
> Well, my belief is that it's growing without bounds.  It starts at
> 13M, jumps to 18M and then gets progressively higher.  It used to grow
> up to 30M-50M or so.
>
> I'm currently experimenting with reducing cache size/time (target=50
> objects / time=10s currently) but I'm not sure that helps yet.  It
> seems to have improved the situation slightly, but we'll only be able
> to tell in a few hours.
>
> > > We're using Zope 2.2.1 with the hotfixes on a Red Hat Linux box.
> > >
> > > Any hints short of switching to another news system appreciated (the
> > > SlashCode guys have been on our case). ;)
> >
> > Don't even think about it!!  :-)
>
> Don't worry, I'll fight it. ;-)
>
> Thanks for the amazingly quick response!
>
> Cheers,
> Navin.
>
>
>