On Fri, 08 Mar 2019 10:42:28 -0500
"wkbrad" <nginx-forum@forum.nginx.org> wrote:

> Thanks for that info. It's definitely harder to notice the issue on
> small servers like that. But you are still seeing about a 50%
> increase in ram usage there by your own tests.
>
> The smallest server I've tested this on uses about 20M during the
> first start and about 50M after a reload is completely finished.
>
> Not so much of a problem for small servers but definitely a big
> problem for large ones. That said the issue is still there on small
> servers like you've just seen.
>
> Posted at Nginx Forum:
> https://forum.nginx.org/read.php?2,283216,283318#msg-283318
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

Actually the total RAM went down after a reload for my ps_mem in the
previous email. I repeated the test just using free, which could be a
polluted test, but the RAM went down again. I also did the ps_mem test
again and total RAM was reduced.

I'm not caching in nginx, if that makes a difference.

sh-4.2# free -m
total used free shared buff/cache available
Mem: 1838 276 175 104 1385 1259
Swap: 0 0 0
sh-4.2# systemctl reload nginx
sh-4.2# free -m
total used free shared buff/cache available
Mem: 1838 272 180 104 1385 1263
Swap: 0 0 0

And repeated ps_mem test:
sh-4.2# ps_mem | grep nginx
2.3 MiB + 3.5 MiB = 5.8 MiB nginx (2)
sh-4.2# systemctl reload nginx
sh-4.2# ps_mem | grep nginx
1.8 MiB + 3.1 MiB = 4.9 MiB nginx (2)


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