Zac Burns wrote:
> I have a server running Python 2.6x64 which after running for about a
> month decides to lock up and become unresponsive to all threads for
> several minutes at a time. While it is locked up Python proceeds to
> consume large amounts of continually increasing memory.
>
> The bas
Paul Rubin wrote:
sturlamolden writes:
Python uses reference counting, not a generational GC like Java. A
Python object is destroyed when the refcount drops to 0. The GC only
collects cyclic references. If you create none, there are no GC delays
(you can in fact safely turn the GC off). Pyt
sturlamolden wrote:
On 9 Sep, 22:28, Zac Burns wrote:
Theories:
Python is resizing the large dictionary
Python is garbage collecting
Python uses reference counting, not a generational GC like Java.
The CPython implementation, that is. Jython, built on top of Java, uses
Java's GC. D
sturlamolden writes:
> Python uses reference counting, not a generational GC like Java. A
> Python object is destroyed when the refcount drops to 0. The GC only
> collects cyclic references. If you create none, there are no GC delays
> (you can in fact safely turn the GC off). Python does not sha
On 9 Sep, 22:28, Zac Burns wrote:
> Theories:
> Python is resizing the large dictionary
> Python is garbage collecting
Python uses reference counting, not a generational GC like Java. A
Python object is destroyed when the refcount drops to 0. The GC only
collects cyclic references. If you
On Wed, Sep 9, 2009 at 6:52 PM, David Stanek wrote:
> On Wed, Sep 9, 2009 at 4:28 PM, Zac Burns wrote:
>>
>> How would you suggest to figure out what is the problem?
>>
>
> I don't think you said your OS so I'll assume Linux.
>
> Sometimes it is more noise than value, but stracing the process may
On Wed, Sep 9, 2009 at 4:28 PM, Zac Burns wrote:
>
> How would you suggest to figure out what is the problem?
>
I don't think you said your OS so I'll assume Linux.
Sometimes it is more noise than value, but stracing the process may
shed light on what system calls are being made. This in turn may
> If it has been running continuously all that time then it might be that
> the dictionary has grown too big (is that possible?) or that it's a
> memory fragmentation problem. In the latter case it might be an idea to
> restart Python every so often; perhaps it could do that automatically
> during
Zac Burns wrote:
I have a server running Python 2.6x64 which after running for about a
month decides to lock up and become unresponsive to all threads for
several minutes at a time. While it is locked up Python proceeds to
consume large amounts of continually increasing memory.
The basic functio
