Christian Boos wrote:
> 
> Jonas Borgström wrote:
>> Christian Boos wrote:
>>
>>> Jeroen Ruigrok van der Werven wrote:
>>>
>>>> -On [20080307 04:31], John Hampton ([EMAIL PROTECTED]) wrote:
>>>>
>>>>
>>>>> Do you think it's possible to have a 0.11b2 release before PyCon?
>>>>>
>>>>>
>>>> Jonas will be testing trunk on t.e.o. this weekend he said.
>>>>
>>
>> t.e.o has now been running trunk for the last 3-4 hours. The memory
>> usage is still a lot higher than 0.10 but seems to be much more stable
>> than our last attempt. One fastcgi process has currently allocated 276MB
>> resident memory. That is a lot more than 0.10.x (Around 120MB) but it
>> seems to have stabilized at that level for the moment.
>>
>> Some details:
>> Trac r6669.
>> Genshi r801.
>> Python 2.4.3 (x86_64)
>>
> 
> I believe you could get some further savings by using Python 2.5.
> Also, I still have a big 45MB log to analyze which I think demonstrates
> a leak, so there might be some more savings to come. Those could
> eventually wait for 0.11-stable if things remain bearable in the meantime.

Unfortunately an hour or two after I sent my precious mail the memory 
usage doubled to around 500MB each for two separate processes.
I'm now experimenting with some gc debugging code on the server in the 
hope of identifying leaky urls. I'll let you know if I find anything.

> So if things seem stable enough, I think we can roll a beta2 or even a
> rc1 at some point next week (I think I'll be done with #5516, #5543 and
> #6609 by then).

I agree, but this latest "incident" shows that there is still some major 
leaks left somewhere. So beta2 might have to wait a while anyway :(

Cheers,
Jonas

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to