Re: [Twisted-Python] debugging a memory leak

2010-02-19 Thread lasizoillo
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

2010-02-19 Thread 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 interpreter process: $ps -orss -p24316

Re: [Twisted-Python] debugging a memory leak

2010-02-19 Thread Werner Thie
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

2010-02-19 Thread Alec Matusis
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

Re: [Twisted-Python] Streaming File Transfer Protocol?

2010-02-19 Thread Darren Govoni
Ignore me. There was a lag, but it worked. Thanks. On Fri, 2010-02-19 at 13:38 -0500, Darren Govoni wrote: > H. I set self.MAX_LENGTH in my subclass > (self.MAX_LENGTH=7376896) but still no callback happens to > strongReceived. Also, the connection is not lost. > > Its like it doesn't no

Re: [Twisted-Python] Streaming File Transfer Protocol?

2010-02-19 Thread Darren Govoni
H. I set self.MAX_LENGTH in my subclass (self.MAX_LENGTH=7376896) but still no callback happens to strongReceived. Also, the connection is not lost. Its like it doesn't notice it on the server, while the client writes successfully. Still investigating. On Fri, 2010-02-19 at 13:12 +,

Re: [Twisted-Python] Streaming File Transfer Protocol?

2010-02-19 Thread Darren Govoni
Jean-Paul, Thank you for this tip! I will try it. Much appreciated. Darren On Fri, 2010-02-19 at 13:12 +, exar...@twistedmatrix.com wrote: > On 11:33 am, dar...@ontrenet.com wrote: > >Hi again, > > Ok, so now it seems the Int32StringReceiver does not receive > >"stringReceived" events i

Re: [Twisted-Python] Streaming File Transfer Protocol?

2010-02-19 Thread exarkun
On 11:33 am, dar...@ontrenet.com wrote: >Hi again, > Ok, so now it seems the Int32StringReceiver does not receive >"stringReceived" events if the sent bytes >exceed a certain amount. If I send from the client, say 5000 bytes. It >receives it. > >But when i send 7376896 bytes at a time, the client

Re: [Twisted-Python] Streaming File Transfer Protocol?

2010-02-19 Thread Darren Govoni
Hi again, Ok, so now it seems the Int32StringReceiver does not receive "stringReceived" events if the sent bytes exceed a certain amount. If I send from the client, say 5000 bytes. It receives it. But when i send 7376896 bytes at a time, the client indicates it wrote the bytes, but there is not

Re: [Twisted-Python] Nevow question

2010-02-19 Thread Marco Giusti
On Fri, Feb 19, 2010 at 03:17:07PM +1100, Sury Soni wrote: > Hi, > > How do we disable traceback on Nevow production site? > > Right now, by default, any nevow site will print full length of > traceback on web browser if there is some exception within the > application. [cut] something like this