Thanks Maxim and Jonathan for making these things clear to me! Disabling disk buffering by using fastcgi_max_temp_file_size 0; and reducing the number of buffers solved the problem and made my service more efficient. Best Regards, Belly Dancerby Belly - Nginx Mailing List - English
Thanks Maxim for you answer! Maxim Dounin Wrote: ------------------------------------------------------- > Hello! > > On Mon, Jun 03, 2013 at 08:57:21AM -0400, Belly wrote: > > > Hello nginx! > > > > I have one worker-process, which uses over 25GB memory (and doesn't > stop to > > do that). > > My configuration is... let's say special:by Belly - Nginx Mailing List - English
Thanks for your reply! I don't have performance issues. It's just the memory usage. I don't know how nginx handles its memory, but if I increase the number of worker processes wouldn't this lead into much higher memory usage (worker_process*25GB) ? The one worker is able to handle all requests, I don't see the point of adding more workers. I want to know why nginx does not free the buffersby Belly - Nginx Mailing List - English
Hello nginx! I have one worker-process, which uses over 25GB memory (and doesn't stop to do that). My configuration is... let's say special: So there is nginx, which proxies all requests to the PHP backend and the PHP backend sends a large request back to nginx. I set the fastcgi_buffers very enormous huge to avoid nginx creating temporary files on my disk - which would result in high CPU lby Belly - Nginx Mailing List - English