Re: Nginx 1.12.1 Memory Consumption

2018-03-19 Thread Peter Booth
I’d use wrk2 or httperf to recreate a spike that hits an http endpoint. If you don’t see a spike but see one with https then you know ssl is one factor. It’s also interesting that this happens st around 23000 connections. If you reduce workr count to one or two And still see max connections aro

Re: Nginx 1.12.1 Memory Consumption

2018-03-19 Thread Maxim Konovalov
Hi Matthew, On 19/03/2018 17:38, Matthew Smith wrote: > Hello, > > The host has 30G total memory. Nginx usage is being measured by > summing the Pss values from /proc/$pid/smaps for all worker processes. > > Do you have any suggestions for differentiating between the two > issues that might prev

Re: Nginx 1.12.1 Memory Consumption

2018-03-19 Thread Matthew Smith
Hello, The host has 30G total memory. Nginx usage is being measured by summing the Pss values from /proc/$pid/smaps for all worker processes. Do you have any suggestions for differentiating between the two issues that might prevent memory from being returned to the system? Thanks! On Thu, Mar 1

Re: Nginx 1.12.1 Memory Consumption

2018-03-15 Thread Peter Booth
Two questions: 1. how are you measuring memory consumption? 2. How much physical memory do you have on your host? Assuming that you are running on Linux, can you use pidstat -r -t -u -v -w -C “nginx” to confirm the process’s memory consumption, and cat /var/meminfo to view a detailed descrip

Re: Nginx 1.12.1 Memory Consumption

2018-03-14 Thread Maxim Dounin
Hello! On Wed, Mar 14, 2018 at 05:05:42PM +, Matthew Smith wrote: > I have encountered what I consider to be an interesting behavior. We have > Nginx 1.12.1 configured to do SSL termination as well as reverse proxy. > Whenever there is a traffic spike (300 req/s > 1000 req/s, 3k active > conn

Nginx 1.12.1 Memory Consumption

2018-03-14 Thread Matthew Smith
Hello, I have encountered what I consider to be an interesting behavior. We have Nginx 1.12.1 configured to do SSL termination as well as reverse proxy. Whenever there is a traffic spike (300 req/s > 1000 req/s, 3k active connections > 20k active connections), there is a corresponding spike in Ngi