memory consumption proxying a comet server

[Arrigo Zanette]

Thank you,
as I said I hope you will solve this annoying problem in future
releases. In the meantime anyone running my same troubles can try the
workaround, or the following.

Indeed, I found that once the flag "chunked_transfer_encoding" is
disabled, also the periodic memory allocations are disabled. However, I
am not fully aware of the consequences: is it safe to use?

Arrigo Zanette

On 05/31/2010 01:41 AM, Maxim Dounin wrote:
> Hello!
>
> On Sat, May 29, 2010 at 08:34:53PM +0200, Arrigo Zanette wrote:
>
>   
>> Hi,
>> when proxying a comet server the http write filter module keeps
>> allocating few bytes for each chunk of data coming from the comet
>> server. These data are freed only when the request terminates, that is
>> possibly never.
>>     
> It's not write filter which allocates memory, and it's not it's 
> business to free it.
>
>   
>> There is also a forum thread (http://forum.nginx.org/read.php?2,73923)
>>  that describes the problem very well.
>>
>> Below I report a workaround that seems working for my application.
>> Basically, I guess if I can free the allocated memory and free it, by
>> rewinding the position in the pool.
>>     
> It's nice it works for you, but obviously it's not something that 
> may be committed.
>
> Maxim Dounin
>
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://nginx.org/mailman/listinfo/nginx-devel
>
>