atom feed17 messages in ru.sysoev.nginxRe: High memory consumption when prox...
FromSent OnAttachments
Rogério SchneiderApr 11, 2010 5:16 pm 
Maxim DouninApr 11, 2010 5:48 pm 
Rogério SchneiderApr 11, 2010 6:07 pm 
Maxim DouninApr 11, 2010 6:56 pm 
Rogério SchneiderApr 11, 2010 8:42 pm 
Maxim DouninApr 12, 2010 12:51 pm 
Rogério SchneiderApr 12, 2010 1:16 pm 
Maxim DouninApr 12, 2010 2:26 pm 
Rogério SchneiderApr 15, 2010 12:42 am 
zanetteaMay 28, 2010 6:54 am 
Rogério SchneiderJun 7, 2010 7:14 pm 
Maxim DouninJun 8, 2010 1:34 am 
zanetteaJun 8, 2010 4:45 am 
Rogério SchneiderJun 8, 2010 7:45 am 
Rogério SchneiderJun 8, 2010 7:54 am 
Igor SysoevJun 8, 2010 8:05 am 
Rogério SchneiderJun 8, 2010 4:57 pm 
Subject:Re: High memory consumption when proxying to a Comet server
From:Rogério Schneider (stoc@gmail.com)
Date:Jun 8, 2010 7:54:24 am
List:ru.sysoev.nginx

The patch I attached actually frees memory before the connection ends but do a
lot of assumptions that might not work. The cleanest solution is probably just
to disable chunked transfer encoding with the option:

chunked_transfer_encoding off;

I am using 0.7.65 and it does not support this option.

which removes the problem at the root (if it is ok for you to disable chunked
transfer encoding, of if you already implement it in the proxied server).

AFAIK nginx does not support memory freeing/reuse before connection ends and,
with current architecture, is not a trivial job to do (requires to handle reuse
of non-contiguous allocations).

Thanks for these pointings, Arrigo.

Regards,