Re: [ZODB-Dev] Extenuated memory

2006-03-24 Thread Antonio Beamud Montero
El jue, 23-03-2006 a las 15:02 -0500, Tim Peters escribió: [Antonio Beamud Montero] But my server doesn't free any memory, now it uses 55Mb of resident size... How I can debug this references? Many layers are involved in memory management, from ZODB through Python down to your platform

Re: [ZODB-Dev] Extenuated memory

2006-03-24 Thread Dieter Maurer
Antonio Beamud Montero wrote at 2006-3-23 09:26 +0100: ... But my server doesn't free any memory, now it uses 55Mb of resident size... How I can debug this references? It has no chance -- and this is neither the fault of Python nor of the ZODB but of C's standard memory management: C does

Re: [ZODB-Dev] Extenuated memory

2006-03-23 Thread Tim Peters
[Antonio Beamud Montero] Well, now I can minimize the cache and get the next values (an unclosed connection fixed): [['BTrees.OOBTree.OOBTree', 3], ['Persistence.PersistentMapping', 6], ['request.Request', 14], ['status.Status', 3]] But my server doesn't free any memory, now it uses 55Mb of

[ZODB-Dev] Extenuated memory

2006-03-22 Thread Antonio Beamud Montero
Hi all: I have implemented a multi-thread server and I have several server as ZEO clients. In the root (ZODB) I have created 3 objects: root['pendings'] = Status() root['error'] = Status() root['completed'] = Status() Where Status is a Persistent Class, with an OOBTree attribute called _dict,

Re: [ZODB-Dev] Extenuated memory

2006-03-22 Thread Dieter Maurer
Antonio Beamud Montero wrote at 2006-3-22 10:56 +0100: ... If I exectue a .minimizeCache(), then the output is: [['request.Request', 504]] But I can't minimize more the cache... Looks as if your application keeps references to your request.Request objects. Check where and get rid of them. --

Re: [ZODB-Dev] Extenuated memory

2006-03-22 Thread Chris Withers
Antonio Beamud Montero wrote: But I can't minimize more the cache... What I need to do to free more memory space, because this always grows... This is a problem with python, I hear rumours it'll be fixed in Python 2.5. cheers, Chris -- Simplistix - Content Management, Zope Python