I had this same problem with the Photo product. I discovered that the photos were being stored as string attributes, vs. a Zope Image object. This means that Zope read the entire string into memory in order to feed it to the browser. Apparently, Zope breaks the data of Image and File objects into pieces to avoid this problem. After modifying the Photo product to use Zope's Image objects, memory use remained low, no matter how many images I uploaded or viewed. I don't know all the ins and outs, but maybe Jonothan Farr can confirm that LocalFS does or does not have this same behavior. _______________________ Ron Bickers Logic Etc, Inc. rbickers@logicetc.com
-----Original Message----- From: galle@zope.org [mailto:galle@zope.org]On Behalf Of Torsten Gallmeister Sent: Wednesday, January 31, 2001 8:19 AM To: zope@zope.org Subject: [Zope] performance problem
could anybody help? Have a perforemance prob. The DB (Data.fs) size is 25 MB. If using ZOPE "normal" the process will be around 35 MB. Ok. Have sopme pdf documents in the presentation. I reduced the DB size with the LocalFS Product. After a search-engine scan over my site the process grows up to 100 MB and more.... The server slows down. ...and there will be some doc's more in future. My question: is there a way to keep the process-size a little smaller?