Memory consumption in case of huge number of configs

[Maxim Dounin]

Hello!

On Tue, Jun 19, 2012 at 10:46:52PM +0400, Valentin V. Bartenev wrote:

> On Tuesday 19 June 2012 19:42:14 dparshin wrote:
> [...]
> > > 
> > > Of course it creates a new pool. Nginx must
> > > continue to work and handle
> > > requests, even if it fails to load the new
> > > configuration.
> > 
> > Sounds reasonable, but unused pool(after reload process successfully
> > finished) is not destroyed,
> 
> Actually it is destroyed. But only after all old workers have finished
> servicing their clients.

No, old cycle's pool is destroyed right after new configuration 
reading, at ngx_init_cycle() end.

(Note that this applies to normal mode of operation with master 
process.  Without master process there are some shims to delay old 
cycle's pool destruction as it might be needed.  This is for 
debugging only though.)

Maxim Dounin