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:Jun 8, 2010 1:34:10 am
List:ru.sysoev.nginx

Hello!

On Mon, Jun 07, 2010 at 11:15:20PM -0300, Rogério Schneider wrote:

On Fri, May 28, 2010 at 10:54 AM, zanettea <ngin@nginx.us> wrote:

I have the very same problem trying to proxying a MJPEG stream. I really would
appreciate a solution not involving periodically resetting the connection.

I have seen your post referring mine, here http://forum.nginx.org/read.php?29,91967,92454 and also have seen this another post related to the matter here http://forum.nginx.org/read.php?2,84623,84623#msg-84623 but no one seems to bother in giving a direct response if that is or isn't possible to free memory for chunked responses BEFORE the connection ends.

No, small allocations can't be freed in nginx. I outlined correct fix as soon as the problem was identified, here:

http://nginx.org/pipermail/nginx/2010-April/019845.html

One should sit and code buffers reuse in chunked module. I have this in my TODO list, but didn't done this yet due to ENOTIME.

Maxim Dounin

_______________________________________________ nginx mailing list ngi@nginx.org http://nginx.org/mailman/listinfo/nginx