AW: High load due to reload

[5hosting GmbH]

Hi Maxim,

thanks for your explanation. Is there a formula we can use to calculate the
amount of RAM needed in a reload scenario?

Thanks, Jürgen

-----Ursprüngliche Nachricht-----
Von: nginx-bounces at nginx.org [mailto:nginx-bounces at nginx.org] Im Auftrag von
Maxim Dounin
Gesendet: Samstag, 04. Juli 2015 08:05
An: nginx at nginx.org
Betreff: Re: High load due to reload

Hello!

On Tue, Jun 23, 2015 at 11:14:44AM +0200, 5hosting GmbH wrote:

> I have a small problem with a nginx system that acts as a 
> loadbalancing proxy. We do have lots of vhosts and ssl certificates 
> and each time we do a /etc/init.d/nginx reload, the load of our server 
> goes up to 20 due to swapping.
> 
> Is there any other way to reload nginx to get aware of ssl or vhost 
> changes without getting high loads?

When reloading a configuration, nginx reads a new configuration and starts
new worker process, and then asks old worker processes to terminate
gracefully.  See this link for a detailed
description:

http://nginx.org/en/docs/control.html#reconfiguration 

This basically means that during configuration reload nginx memory
consumption grows up for a while (and roughly doubles in some cases).  You
should tune your system appropriately to make sure there are enough memory
to start new worker processes without swapping.  In particular, if most of
the memory is used for nginx buffers (proxy_buffers, proxy_buffer_size, and
so on), tuning these buffers usually is enough.

--
Maxim Dounin
http://nginx.org/

_______________________________________________
nginx mailing list
nginx at nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6079 bytes
Desc: not available
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20150706/b3fe6f1f/attachment.bin>