[Zope] Zope memory usage out of control and Photo product

Ron Bickers rbickers@logicetc.com
Tue, 6 Feb 2001 03:01:14 -0500


More easily than I imagined, I modified the Photo product to use Image
objects instead of string attributes to store the various display sizes.
The result... my Zope process is now using ~15MB of memory instead of the
100+MB it used before.  I guess I've answered my own question by example.

If anyone uses the Photo product and would like my "fix", let me know.  The
fix will convert existing Photo objects so you don't have to redo anything.
In case anyone is interested in a plain Photo product example, I'm building
a house and have over a hundred photos of the process at
http://www.bickersfamily.org/Photos/House.  The Photo product (and a digital
camera) made it very easy to throw something half usable together, and my
modifications make it far less hungry.

Thanks again Chris for that final nugget of info I needed.
_______________________

Ron Bickers
Logic Etc, Inc.
rbickers@logicetc.com


> -----Original Message-----
> From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Ron
> Bickers
> Sent: Tuesday, February 06, 2001 1:03 AM
> To: Chris McDonough; Navindra Umanee; zope@zope.org
> Subject: RE: [Zope] Zope memory usage out of control

> After finally studying the Photo code, I discovered that the
> different sized
> images are each stored as object attributes (strings using
> StringIO), not as
> separate Image objects.  So each object has about 6 different
> strings, each
> the length of the image of that display size.
>
> It seems that this type of object would cause Zope to eat my memory.  Can
> someone verify that this would do it?  I'll be a happy camper if
> this is the
> problem.  I can change the Photo product to store them as Image
> objects and
> hopefully get my memory back.