Re: [Twisted-Python] debugging a memory leak

com] On Behalf Of exar...@twistedmatrix.com > Sent: Thursday, February 25, 2010 4:51 PM > To: Twisted general discussion > Subject: Re: [Twisted-Python] debugging a memory leak > > On 01:24 am, johann.bo...@densedata.com wrote: > >Alec Matusis wrote: > >>In desperation of not findi

Re: [Twisted-Python] debugging a memory leak

On 01:24 am, johann.bo...@densedata.com wrote: >Alec Matusis wrote: >>In desperation of not finding the real memory leak on the production >>server, >> >>I wrote a test server that I can push to arbitrary high RSS memory. I >>am far >>from sure if this the same leak that I observe in production,

Re: [Twisted-Python] debugging a memory leak

Alec Matusis wrote: > In desperation of not finding the real memory leak on the production server, > > I wrote a test server that I can push to arbitrary high RSS memory. I am far > from sure if this the same leak that I observe in production, but I would > like to understand what this one is. > T

Re: [Twisted-Python] debugging a memory leak

python-boun...@twistedmatrix.com [mailto:twisted-python- > boun...@twistedmatrix.com] On Behalf Of Werner Thie > Sent: Monday, February 22, 2010 11:39 PM > To: Twisted general discussion > Subject: Re: [Twisted-Python] debugging a memory leak > > Hi > > Assuming that if

Re: [Twisted-Python] debugging a memory leak

edmatrix.com [mailto:twisted-python- >> boun...@twistedmatrix.com] On Behalf Of Maarten ter Huurne >> Sent: Monday, February 22, 2010 6:24 PM >> To: Twisted general discussion >> Subject: Re: [Twisted-Python] debugging a memory leak >> >> On Tuesday 23 February 2010, Ale

Re: [Twisted-Python] debugging a memory leak

Message- > From: twisted-python-boun...@twistedmatrix.com [mailto:twisted-python- > boun...@twistedmatrix.com] On Behalf Of Maarten ter Huurne > Sent: Monday, February 22, 2010 6:24 PM > To: Twisted general discussion > Subject: Re: [Twisted-Python] debugging a memory leak > > On T

Re: [Twisted-Python] debugging a memory leak

On Tuesday 23 February 2010, Alec Matusis wrote: > When I start the process, both python object sizes and their counts rise > proportionally to the numbers of reconnected clients, and then they > stabilize after all clients have reconnected. > At that moment, the "external" RSS process size is abo

Re: [Twisted-Python] debugging a memory leak

x.com [mailto:twisted-python- > boun...@twistedmatrix.com] On Behalf Of Werner Thie > Sent: Friday, February 19, 2010 4:10 PM > To: Twisted general discussion > Subject: Re: [Twisted-Python] debugging a memory leak > > Hi Alec > > ...and they promised you that with a gc'e

Re: [Twisted-Python] debugging a memory leak

2010/2/20 Alec Matusis : > Thank you Werner! > > I am playing with your object counter. But before I can interpret the > results, I have to ask a possibly stupid question. > Can someone explain to me this behavior of python 2.6 on x86 linux 2.6.24: > > 1) start interpreter > Check the size of the i

Re: [Twisted-Python] debugging a memory leak

nal Message- > From: twisted-python-boun...@twistedmatrix.com [mailto:twisted-python- > boun...@twistedmatrix.com] On Behalf Of Werner Thie > Sent: Friday, February 19, 2010 4:10 PM > To: Twisted general discussion > Subject: Re: [Twisted-Python] debugging a memory leak > > Hi Al

Re: [Twisted-Python] debugging a memory leak

Hi Alec ...and they promised you that with a gc'ed language there will never be a memory problem again, you just plain forget about it. I was stuck in the same position as you and after lots of probing the following attempt helped a lot to correct what was later proofed to be overly optimistic

[Twisted-Python] debugging a memory leak

I modified a tolerably leaking (about 40MB/day) Twisted server: when the new code was pushed, the memory leak became catastrophic (about 100MB/hr). We could tolerate 40MB/day, but the new code needs to be debugged. First, I reverted to the old version, that is leaking 40MB/day (The leak rate is ac