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:Maxim Dounin (mdou@mdounin.ru)
Date:Apr 11, 2010 5:48:52 pm
List:ru.sysoev.nginx

Hello!

On Sun, Apr 11, 2010 at 09:16:33PM -0300, Rogério Schneider wrote:

When proxying to a Comet server, I was able to notice that Nginx is eating and not releasing a massive amount of memory.

As we all know, Comet servers can have this "streaming" mode, where we receive a chunked HTTP request that never ends.

Is there some problem that avoids Nginx to release memory when in proxy mode, before the connection ends at all?

[...]

nginx does memory allocations on per-request basis, and frees memory when request ends. Though after sending response headers possible allocations are limited by various *_buffers settings.

For proxied requests you may want to make sure your proxy_buffers aren't set too high, see here:

http://wiki.nginx.org/NginxHttpProxyModule#proxy_buffers